6man w.g., The 6man chairs believe the working group has reached a consensus on advancing this version of the update to Node Requirements to the IESG. The current discussion on the list relating to SLAAC and DHCPv6 is out of scope for the Node Requirements document. There is more involved in the discussion than can be dealt with by changing requirements language as would be appropriate for the Node Requirements document.
We plan to advance <draft-ietf-6man-node-req-bis-10.txt> to the IESG later today. Regards, Bob Hinden & Brian Haberman 6man Chairs Begin forwarded message: > From: Thomas Narten <[email protected]> > Date: May 23, 2011 9:18:04 AM PDT > To: [email protected] > Subject: Re: I-D Action: draft-ietf-6man-node-req-bis-10.txt > > WG, > > I believe this version is ready to advance to the IESG. > > From the changes section: > >> 17.1. Appendix: Changes from -09 to -10 >> >> 1. With changes in requirements for IPsec and Routing Headers, >> clarified language regarding processing of unknown options, and >> removed paragraph lising which extension headers were required to >> be implemented. > > Above changes are in Section 5.1. > >> 2. Removed "RFC4292-bis" from title. >> 3. Expanded the text on Jumbograms. >> 4. Changed recommendation of DHCPv6 from MAY to SHOULD. >> 5. Expanded the text on RFC4191, and changed recommendation from MAY >> to SHOULD. > > The last 3 changes have recently been discussed on the mailing list. > > Thomas > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
