Last Call Review of draft-ietf-dhc-dhcpv6-unknown-msg-05
review-ietf-dhc-dhcpv6-unknown-msg-05-secdir-lc-lonvick-2014-03-13-00
Request | Review of | draft-ietf-dhc-dhcpv6-unknown-msg |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2014-03-18 | |
Requested | 2014-02-06 | |
Authors | Yong Cui , Qi Sun , Ted Lemon | |
I-D last updated | 2014-03-13 | |
Completed reviews |
Genart Last Call review of -05
by Suresh Krishnan
(diff)
Genart Telechat review of -06 by Suresh Krishnan (diff) Secdir Last Call review of -05 by Chris M. Lonvick (diff) Opsdir Telechat review of -05 by Carlos Pignataro (diff) |
|
Assignment | Reviewer | Chris M. Lonvick |
State | Completed | |
Request | Last Call review on draft-ietf-dhc-dhcpv6-unknown-msg by Security Area Directorate Assigned | |
Reviewed revision | 05 (document currently at 08) | |
Result | Has issues | |
Completed | 2014-03-13 |
review-ietf-dhc-dhcpv6-unknown-msg-05-secdir-lc-lonvick-2014-03-13-00
Hi, I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This document looks to be well thought out and almost complete. I would like to see a statement in the Security Considerations section that this specification adheres to the Security Considerations section of RFC 3315, and augments it by describing the disposition of unknown messages. Other than that, the only very minor nit that I have is that the second and third paragraphs of the Security Considerations section are a single thought and should be combined. Thanks, Chris