[dhcwg] I-D Action: draft-ietf-dhc-rfc3315bis-05 published

FYI

This -05 version contains the combined work of the team. Here are the
major changes since -04 (excerpt from ChangeLog in Appendix A):

62.  Merged sections 17, 18 and 19 into a single section describing
     client and server behaviors.  Ticket #142.

63.  Added text about single session for multiple IA option types.
     Ticket #160.

64.  Moved additional text from RFC3633 section 12.1.  Ticket #102.

65.  Addressed minor addition to text as per ticket 131 and also
     ticket #61.

66.  Clarified MUST perform DAD, excepting exceptions listed in
     RFC4862 Section 5.4.  Ticket #153.

67.  Removed the requirement for the server to send Reconfigure
     Accept in Reply messages, also clarified why it's useful in
     Advertise.  Ticket #154.

68.  Explicitly require Elapsed Time option to be placed in messages
     sent by a client.  Ticket #159.

69.  Update section 14 - explained that Elapsed Time option (and
     possibly other options) must be updated prior to resending the
     message.  Also included "retransmission" in the DHCP
     terminology.  Ticket #157.

70.  Added text explaining that the client should stop using an
     option if it's not being sent by the server.  Ticket #150.

71.  Added reference to RFC4242 (Information Refresh Time Option).
     Ticket #161.

72.  Updated ORO Option to list Options that MUST NOT be included.
     Also added to that IANA Consider should keep track of which
     options are allowed in ORO.  Ticket #81.

73.  Updated Creation and Transmission of Advertise message so that
     the only options in the ORO will be included in the Advertise
     unless configured otherwise.  Ticket #81.

74.  Information Refresh Time Option is now mandatory for clients
     that support stateless mode.  Added reference to RFC4242.
     Ticket #161.

Please take a look at the diff tool
(https://tools.ietf.org/rfcdiff?url2=draft-ietf-dhc-rfc3315bis-05.txt)
for all changes
since -04. If you'd like to get more details regarding the tickets, they
can be viewed at https://tools.ietf.org/group/dhcpv6bis/.

Bernie and I will discuss the next steps, but our intention is to start
WGLC shortly. Since both of us are co-authors, we may be able to start
it on our own, but we will ask the shepherd to determine the consensus
after WGLC is done. Also, this is a complex and essential document, so
we need to give enough time for people to review it thoroughly. Expect
much longer WGLC than usual. Details are TBD.

Tomek

-------- Forwarded Message --------
Subject: [dhcwg] I-D Action: draft-ietf-dhc-rfc3315bis-05.txt
Date: Mon, 27 Jun 2016 05:46:56 -0700
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
CC: dhcwg@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Dynamic Host Configuration of the IETF.

        Title           : Dynamic Host Configuration Protocol for IPv6
(DHCPv6) bis
        Authors         : Tomek Mrugalski
                          Marcin Siodelski
                          Bernie Volz
                          Andrew Yourtchenko
                          Michael C. Richardson
                          Sheng Jiang
                          Ted Lemon
                          Timothy Winters
	Filename        : draft-ietf-dhc-rfc3315bis-05.txt
	Pages           : 134
	Date            : 2016-06-27

Abstract:
   This document describes the Dynamic Host Configuration Protocol for
   IPv6 (DHCPv6): an extensible mechanism for configuring hosts with
   network configuration parameters, IP addresses, and prefixes.
   Parameters can be provided statelessly, or in combination with
   stateful assignment of one or more IPv6 addresses and/or IPv6
   prefixes.  DHCPv6 can operate either in place of or in addition to
   stateless address autoconfiguration (SLAAC).

   This document updates the text from RFC 3315, the original DHCPv6
   specification, and incorporates the stateless DHCPv6 extensions (RFC
   3736) and prefix delegation (RFC 3633), clarifying the interactions
   between these modes of operation (RFC 7550) and providing a mechanism
   for throttling DHCPv6 clients when DHCPv6 service is not available
   (RFC 7083).  As such, this document obsoletes RFC3315, RFC3633,
   RFC3736, RFC7083, RFC7550.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-rfc3315bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-rfc3315bis-05

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg