Telechat Review of draft-ietf-dhc-rfc3315bis-10
review-ietf-dhc-rfc3315bis-10-opsdir-telechat-romascanu-2017-12-29-00
| Request | Review of | draft-ietf-dhc-rfc3315bis |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | Telechat Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2018-01-09 | |
| Requested | 2017-11-28 | |
| Authors | Tomek Mrugalski , Marcin Siodelski , Bernie Volz , Andrew Yourtchenko , Michael Richardson , Sheng Jiang , Ted Lemon , Timothy Winters | |
| I-D last updated | 2017-12-29 | |
| Completed reviews |
Intdir Early review of -10
by Zhen Cao
(diff)
Genart Telechat review of -10 by Elwyn B. Davies (diff) Secdir Telechat review of -10 by Kyle Rose (diff) Opsdir Telechat review of -10 by Dan Romascanu (diff) Tsvart Telechat review of -10 by Allison Mankin (diff) |
|
| Assignment | Reviewer | Dan Romascanu |
| State | Completed | |
| Request | Telechat review on draft-ietf-dhc-rfc3315bis by Ops Directorate Assigned | |
| Reviewed revision | 10 (document currently at 13) | |
| Result | Ready | |
| Completed | 2017-12-29 |
review-ietf-dhc-rfc3315bis-10-opsdir-telechat-romascanu-2017-12-29-00
This document updates RFC3315, the original DHCPv6 specification, incorporates a number of new mechanisms and extensions that were defined in the period since the publication RFC 3315, clarifies a number of items, and obsoletes RFC 3315 and five other supporting RFCs. A small number of mechanisms that were obsoleted, listed in Section 25, and the changes relative are summarized in Appendix A. As this document does not define a new protocol, or a significant different versions of the existing protocol, but rather documents, clarifies and consolidates a technology that is widely deployed in the Internet, there are no new operational or manageability considerations to be described or added. It's a very useful document for network operators, who should start using it as a reference instead of the the obsolete RFCs and errata as soon as it is published. This document is READY from an OPSDIR perspective.