Last Call Review of draft-ietf-isis-rfc4971bis-01
review-ietf-isis-rfc4971bis-01-secdir-lc-sheffer-2016-08-11-00
| Request | Review of | draft-ietf-isis-rfc4971bis |
|---|---|---|
| Requested revision | No specific revision (document currently at 04) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2016-08-15 | |
| Requested | 2016-08-04 | |
| Authors | Les Ginsberg , Stefano Previdi , Mach Chen | |
| I-D last updated | 2016-10-19 (Latest revision 2016-08-18) | |
| Completed reviews |
Genart IETF Last Call review of -01
by Dale R. Worley
(diff)
Genart IETF Last Call review of -01 by Dale R. Worley (diff) Secdir IETF Last Call review of -01 by Yaron Sheffer (diff) Opsdir Telechat review of -01 by Ron Bonica (diff) |
|
| Assignment | Reviewer | Yaron Sheffer |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-isis-rfc4971bis by Security Area Directorate Assigned | |
| Reviewed revision | 01 (document currently at 04) | |
| Result | Ready | |
| Completed | 2016-08-11 |
review-ietf-isis-rfc4971bis-01-secdir-lc-sheffer-2016-08-11-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. This document is a minor update to RFC4971, in order to correctly support IPv6-only routers. Summary The document is ready for publication. Details The Security Considerations are unchanged from the original RFC and cover the router capability feature reasonably. They still seem to describe this quaint world where each router can rely on all its peers to always send correct information. But at least we recommend to use protocol-level integrity mechanisms in "high risk" situations. Thanks, Yaron