This revision primarily has editorial changes & clarifications in response to IESG comments. There are also two substantive changes that require WG review:
1. I added definitions and requirements for IPv4-mapped and IPv4-translatable addresses, in support of SIIT. The key paragraph is On IPv6-only nodes that support SIIT [13, especially section 5], if the destination address is an IPv4-mapped address then the candidate set MUST contain only IPv4-translatable addresses. If the destination address is not an IPv4-mapped address, then the candidate set MUST NOT contain IPv4-translatable addresses. I believe this change has already has WG consensus, based on discussion on the list late last year and at Salt Lake City. I just forgot to incorporate it earlier. 2. I changed the requirement for an API to control temporary vs public address usage, from "may" to "MUST". The new text reads An implementation MUST support a per-connection configuration mechanism (for example, a socket option) to reverse the sense of this preference and prefer temporary addresses over public addresses. The default is still to use public addresses not temporary addresses, although implementations MAY reverse this default if they want to emphasize privacy over application compatibility. Thanks, Rich -------------------------------------------------------------------- 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] --------------------------------------------------------------------
