Rajiv Raghunarayan wrote on 08/22/2004 02:48:25 AM:
> Greetings folks,
> [Bcced: Brian Haberman, Bob Hinden, Margaret Wasserman, Bert Wijnen]
> During the IESG review of the UDP-MIB a small problem was
> identified, resulting from the MIB being incompatible with
> the definitions in draft-3291bis (draft-ietf-ops-rfc3291bis-06).
> I've described the problem below, but the same problem plagues
> the TCP-MIB as well.
> The problem is in the following statement made in the TCP-MIB::
> tcpListenerTable description clause:
> <snip>
> 2. An application which is willing to accept only IPv4 or
> IPv6 datagrams is represented by a
> tcpListenerLocalAddressType of the appropriate address
> type and tcpListenerLocalAddress of ''h (a zero-length
> octet-string).
> <snip>
> However, RFC 3291 (& draft-ietf-ops-rfc3291bis-06.txt) allows
> a zero-length octet-string to be specified only with an
> InetAddressType 'unknown'. With address type IPv4 or IPv6 the
> expected length of the address is 4 & 16 octets respectively.
> A similar problem also exists in the definition of TCP-MIB::
> tcpListenerLocalAddress.
> The fix for this is to replace the requirement of the 0-length
> octet string with an ip address 0.0.0.0 (for IPv4) and :: (for
> IPv6). Detailed modification listed at the end of this mail.
> We propose to make this modification at the AUTH48 time.
> Appreciate if you could let me know if you see any issues with
> this change.
Hello,
In this case, would it be better to update draft-3291bis to permit zero-length octet-strings for InetAddress objects whose InetAddressType is IPv4 or IPv6? We have already encountered problems with network management applications not being able to get as much SNMP data back in an SNMP response as they would like to be able to. With an IPv6 address in an instance already taking up a lot of space in the SNMP response packet, it doesn't seem like a good use of response packet space to return 16 bytes of zeros for the address.
Thanks,
Kristine Adamson
IBM z/OS Communications Server: TCP/IP Development
Phone: (919) 254-7911 T/L 444-7911
Internet e-mail:[EMAIL PROTECTED]
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
