Re: draft-ops-endpoint-mib-06.txt

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

>>>>> Glenn Mansfield writes:

>> An InetAddress value is always interpreted within the context of an
>> InetAddressType value. When this Textual Convention is used, then
>> the DESCRIPTION clause MUST specify which associated object
>> specifies the context for the InetAddress value.

Glenn> Do we really need this ?  This description may lead one to
Glenn> think that InetAddressType can be shared.  That is of course
Glenn> explicitly forbidden in the Usage Hints section below.

I agree. The text is from the old version where we did not have a rule
to identify the corresponding InetAddressType value. I propose to
remove the last sentence quoted above and to add text to the
DESCRIPTION clauses of InetAddress and InetAddressType along the lines
of what is currently in the Usage Hints section (see below).

>>   Internet addresses MUST always be represented by a pair of
>>   InetAddressType/InetAddress objects. It is not allowed to "share" an
>>   InetAddressType between multiple InetAddress objects. Furthermore,
>>   the InetAddressType object must be registered immediately before the
>>   InetAddress object. In other words, the OIDs for the InetAddressType
>>   object and the InetAddress object MUST have the same length and the
>>   last sub-identifier of the InetAddressType object MUST be 1 less
>>   than the last sub-identifier of the InetAddress object. 

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>