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

["Glenn Mansfield" <glenn@cysol.co.jp>]

Jurgen,
        Thanks for the reply. I am glad that we concur on the
comments below.

         Cheers

          Glenn
>
>>   InetAddressType ::= TEXTUAL-CONVENTION
>>       STATUS      current
>>       DESCRIPTION
>>           "A value that represents a type of Internet address.
>>
>>            unknown(0)  An unknown address type. This value MUST
>>                        be used if the value of the corresponding
>>                        InetAddress object is a zero-length string.
>>                        It may also be used to indicate an IP address
>>                        which is not in one of the formats defined
>>                        below.
>>
>>            ipv4(1)     An IPv4 address as defined by the
>>                        InetAddressIPv4 textual convention.
>>
>>            ipv6(2)     An IPv6 address as defined by the
>>                        InetAddressIPv6 textual convention.
>>
>>            dns(16)     A DNS domain name as defined by the
>>                        InetAddressDNS textual convention.
>>
>>            Each definition of a concrete InetAddressType value must be
>>            accompanied by a definition of a textual convention for use
>>            with that InetAddressType.
>>
>>            The InetAddressType textual convention SHOULD NOT be subtyped
>>            in object type definitions to support future extensions. It
>>            MAY be subtyped in compliance statements in order to require
>>            only a subset of these address types for a compliant
>>            implementation."
>>       SYNTAX      INTEGER {
>>                       unknown(0),
>>                       ipv4(1),
>>                       ipv6(2),
>>                       dns(16)     -- align with AddressFamilyNumbers in
>>                   }               -- IANA-ADDRESS-FAMILY-NUMBERS-MIB
>>
>>
>>
>>Daniele, et. al.          Expires July 1, 2000                  [Page 7]
>> 
>>Internet-Draft     TCs for Internet Network Addresses       January 2000
>>
>>
>>   InetAddress ::= TEXTUAL-CONVENTION
>>       STATUS       current
>>       DESCRIPTION
>>           "Denotes a generic Internet address.
>>
>>            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.
>Do we really need this ?
>This description may lead one to think that InetAddressType can be shared.
>That is ofcourse explicitly forbidden in the Usage Hints section below.
>>
>
>>4. Usage Hints
>>
>>   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. 
>
>Glenn
>
>
>
>
>