I have two meta-comments and two specific comments on this document: 1) (meta-comment) The specification speaks of only two classes of unicast addresses (link-local and global) but we now have a third class (ULAs - RFC4193) and others may be definied in the future (e.g., PI). The term "global (address)" should therefore be somehow relaxed throughout the document to allow for stateless autoconfiguration of non-link-local unicast addresses other than just normal global addresses.
2) (meta-comment) Section 5.4 introduces new text that disallows the optimization of testing for uniqueness of link-locals only and skipping the test for additional addresses. Therefore, new implementations will need to do DAD for addresses that derive from both organic information (link-locals) and information learned from the network (non-link-locals). This suggests that the configuration variable 'DupAddrDetectTransmits' is over- loaded in the new specification since DAD considerations for link-locals and non-link-locals may be different in some environments. Suggested fix is to split the configuration variable into two separate variables ('DupAddrDetectTransmits' and 'DupAddrDetectTransmitsLL') with the former used for DAD tests of non-link-locals and the latter used for DAD tests of link-locals. New implememtations would use the separate variables, and existing implementations would continue to use the single variable. Text changes throughout the document for consistency also required. 3) (specific) Section 5.3, third bullet, second sentence, change to: "This includes the case where the attached link is dynamically changed, e.g., due to a change of the access point of wireless networks." 4) (specific) Section 5.5.3, item d), the phrase: "configured by stateless autoconfiguration" - why was this phrase added? Prefer that it be removed. Fred [EMAIL PROTECTED] -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------