Kristine,
I'm sorry I missed your email the first time you sent it.
> For a server application
> that opens an AF_INET6 socket and binds to the unspecified address (without
> setting the IPv6_V6ONLY socket option), should there be two entries in
> these MIB tables, one with the local address as IPv4/INADDR_ANY and one
> with the local address as IPv6/unspecified? Or should there be one entry
> with the local address as IPv6/unspecified?
This is one of the open issues. I think we've been leaning towards
InetAddressType == Unknown, and a zero-length InetAddress.
> What if the server application
> opened an AF_INET6 socket and bound to an IPv4-mapped address? Would there
> be one entry in the tables with the local address as IPv4/address or as
> IPv6/IPv4-mapped address?
This is a good question, and one which I hadn't thought of.
There should be a canonical answer, since otherwise managers will have
to check both IPv4 and IPv6-mapped addresses if they're looking for a
specific row. That implies that the answer should represent the AF
on the wire, not necessarily the socket, and perhaps the MIBs should
prohibit using InetAddressType=ipv6 and IN6_IS_ADDR_V4MAPPED(InetAddress).
Bill
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
