Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis
|2015-10-14||04||(System)||Notify list changed from firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com to (None)|
This document was adopted by the WG after a call for Adoption (started Feb 22, 2015, concluding March 9, 2015). There were no objections to ...
This document was adopted by the WG after a call for Adoption (started Feb 22, 2015, concluding March 9, 2015). There were no objections to adopting the document. The document is also a charter work item.
|2015-03-11||04||Bernie Volz||IETF WG state changed to Adopted by a WG from Call For Adoption By WG Issued|
|2015-02-22||04||Bernie Volz||IETF WG state changed to Call For Adoption By WG Issued from Candidate for WG Adoption|
|2015-02-22||04||Bernie Volz||Intended Status changed to Internet Standard from None|
As you all know, the work to update the DHCPv6 specs, mainly RFC3315 and RFC3633, has been going for some time. The design team ...
As you all know, the work to update the DHCPv6 specs, mainly RFC3315 and RFC3633, has been going for some time. The design team involved in this work believes that it's a good time to ask for adoption of this work.
The document - draft-dhcwg-dhc-rfc3315bis-04 (https://tools.ietf.org/html/draft-dhcwg-dhc-rfc3315bis) - started from a XMLized copy of RFC3315 (see the -00 draft). Most of the text from RFC3633 was merged (note: there are still missing pieces) there. A significant number of corrections, clarifications and smaller edits were made. The changes are documented in appendices A and B. They often mention ticket numbers. Those tickets can be reviewed and commented at http://wiki.tools.ietf.org/group/dhcpv6bis/.
As both DHC WG chairs, DHC secretary, and current AD are co-authors of this draft, we'll not be able to assess consensus on our own. We will consult with our AD to determine the best course of action. In any case, the adoption call consensus will be determined shortly after end of day March 9th. (Though if there are no objections, the consensus is clear.)
Keep in mind that this is a work well in progress with lots of outstanding things to do. The question here is whether this is the direction we, as a working group, want to take.
There's also an additional question if you support adoption. Every time a ticket is added, modified or commented in the issue tracker, there's a mail notification. Currently such notifications are sent to the dhcpv6bis mailing list. You can review those here:
http://www.ietf.org/mail-archive/web/dhcpv6bis/current/maillist.html. If you want those notifications to be sent to the DHC rather than dhcpv6bis list, please say so.
- Bernie & Tomek
|2015-02-22||04||Bernie Volz||IETF WG state changed to Candidate for WG Adoption|
|2015-02-22||04||Bernie Volz||Notification list changed to firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org|
|2015-02-22||04||Bernie Volz||Changed group to Dynamic Host Configuration (DHC)|
|2015-02-22||04||Bernie Volz||Changed stream to IETF|
|2015-02-22||04||Tomek Mrugalski||New version available: draft-dhcwg-dhc-rfc3315bis-04.txt|
|2014-10-27||03||Bernie Volz||New version available: draft-dhcwg-dhc-rfc3315bis-03.txt|
|2014-07-04||02||Tomek Mrugalski||New version available: draft-dhcwg-dhc-rfc3315bis-02.txt|
|2014-05-19||01||Bernie Volz||New version available: draft-dhcwg-dhc-rfc3315bis-01.txt|
|2014-03-02||00||Ted Lemon||Ballot writeup was changed|
|2014-03-02||00||Ted Lemon||Ballot writeup was generated|
|2014-01-08||00||Bernie Volz||New version available: draft-dhcwg-dhc-rfc3315bis-00.txt|