Last Call Review of draft-leiba-3967upd-downref-01
review-leiba-3967upd-downref-01-secdir-lc-yu-2016-12-01-00
Request | Review of | draft-leiba-3967upd-downref |
---|---|---|
Requested revision | No specific revision (document currently at 03) | |
Type | IETF Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2016-11-15 | |
Requested | 2016-10-20 | |
Authors | Barry Leiba | |
I-D last updated | 2017-01-24 (Latest revision 2016-12-09) | |
Completed reviews |
Genart IETF Last Call review of -00
by Peter E. Yee
(diff)
Genart Telechat review of -00 by Peter E. Yee (diff) Secdir IETF Last Call review of -01 by Taylor Yu (diff) Opsdir IETF Last Call review of -03 by Will (Shucheng) LIU |
|
Assignment | Reviewer | Taylor Yu |
State | Completed | |
Request | IETF Last Call review on draft-leiba-3967upd-downref by Security Area Directorate Assigned | |
Reviewed revision | 01 (document currently at 03) | |
Result | Has nits | |
Completed | 2016-12-01 |
review-leiba-3967upd-downref-01-secdir-lc-yu-2016-12-01-00
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. Summary: ready with nits The Security Considerations changes added in -01 seem good. Comment: Could the responsible AD annotate each "safe" normative downref (doesn't require community review), along with the rationale? (e.g., foundational or architecture document having Informational status) Or is that putting too much burden on the AD? I know this is a substantive comment late in the process, so feel free to disregard. -Tom