Re: [ipv6mib] please post these internet drafts

[Michael Daniele <daniele@zk3.dec.com>]

hi juergen,

   transportDomainUdpIpv4z OBJECT-IDENTITY
       STATUS      current
       DESCRIPTION
           "The UDP over IPv4 transport domain.  The corresponding
            transport address is of type TransportAddressIPv4z for
            non-global IPv4 addresses."
       ::= { transportDomains 3 }

i suggest "for IPv4 addresses with an associated zone index" instead of
"for non-global IPv4 addresses".

   transportDomainUdpIpv6z OBJECT-IDENTITY
       STATUS      current
       DESCRIPTION
           "The UDP over IPv6 transport domain.  The corresponding
            transport address is of type TransportAddressIPv6z for
            non-global IPv6 addresses."
       ::= { transportDomains 4 }

i suggest "for IPv6 non-global addresses with an associated zone index" instead
of
"for non-global IPv6 addresses".  (a non-global address does not necessarily 
have an associated zone index, right?)

the same for their TCP counterparts.

 3.1.3 INET-ADDRESS-MIB (InetAddressType, InetAddress)

   The INET-ADDRESS-MIB module [18] defines the textual conventions
   InetAddressType and InetAddress to represent Internet network layer
   endpoints.

i'd change "endpoints" to "addresses".

   with the InetPortNumber textual convention to represent Internet
   transport layer endpoints.  This is approach is fine as long as a MIB
   models protocols or applications that are specific to the Internet
   suite of transport protocols.  For protocols or applications that can
   potentially use other transport protocols, the use of the definitions
   contained in this memo is more appropriate.

i think we should recommend the use of the TRANSPORT-ADDRESS-MIB definitions 
for transport endpoints.

mike