On Sat, May 22, 2004 at 05:22:32PM +0300, [EMAIL PROTECTED] wrote: > > > Should we not update this before it goes final with the wording that has > > been agreed for the M and O flags, and also to clarify the assertion below, > > that RAs are the way to get default router and onlink prefix information? > > > > It would be a shame to not convey this consensus in the nodes document. > > In the draft, that's at least section 4.5.2 and 4.5.5 that probably need a > > tweak. > > Take a look at the current draft, a copy can be found here: > http://www-nrc.nokia.com/sua/draft-ietf-ipv6-node-requirements-09.txt > > and let me know what you think should be modified. Please note that > the idea was that this document should not update any existing RFCs, > so we cannot prescribe new behavior.
Ah, good point. However, the 2462 update is due to be submitted very soon, so is it worth waiting on that one to get the more appropriate text in this nodes document? Regarding changes, there would be three I'd suggest. The first two point into 2462-bis, so we just need to (as Christian would say) use the "less is more" maxim, so do something like this: 1. In 5.3.1 change "IPv6 Nodes that use DHCP for address assignment initiate DHCP to obtain IPv6 addresses and other configuration information upon receipt of a Router Advertisement with the 'M' flag set, as described in section 5.5.3 of RFC 2462." to "The method by which IPv6 Nodes that use DHCP for address assignment can obtain IPv6 addresses and other configuration information upon receipt of a Router Advertisement with the 'M' flag set is described in section 5.5.3 of RFC 2462." (leaves the suggestion of M being "mandatory" without using the "MAY" term) 2. In 5.3.2 change "Those IPv6 Nodes that use DHCP to obtain other configuration information initiate DHCP for other configuration information upon receipt of a Router Advertisement with the 'O' flag set, as described in section 5.5.3 of RFC 2462." to "The method by which IPv6 Nodes that use DHCP to obtain other configuration information can obtain other configuration information upon receipt of a Router Advertisement with the 'O' flag set is described in section 5.5.3 of RFC 2462." (ideally that "can" would be a "may", but that suggests something that is not finalised yet, so would be a change of meaning, which you don't want) 3. Add a section 5.5.3: "5.3.3 Use of Router Advertisements in Managed Environments Nodes using the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) are expected to determine their default router information and on-link prefix information from received Router Advertisements." (Perhaps some people may think this is saying too much, or the section heading could be improved, but if the opinion on the list is consensus, we should add it? You may wish to add reference to Stateless DHCPv6 in that extra section too?) Tim -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
