Last Call Review of draft-ietf-sidr-origin-ops-21
review-ietf-sidr-origin-ops-21-secdir-lc-yu-2013-11-21-00
Request | Review of | draft-ietf-sidr-origin-ops |
---|---|---|
Requested revision | No specific revision (document currently at 23) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2013-11-19 | |
Requested | 2013-09-19 | |
Authors | Randy Bush | |
I-D last updated | 2013-11-21 | |
Completed reviews |
Genart Last Call review of -21
by Robert Sparks
(diff)
Genart Telechat review of -22 by Robert Sparks (diff) Secdir Last Call review of -21 by Taylor Yu (diff) Opsdir Telechat review of -22 by Al Morton (diff) |
|
Assignment | Reviewer | Taylor Yu |
State | Completed | |
Review |
review-ietf-sidr-origin-ops-21-secdir-lc-yu-2013-11-21
|
|
Reviewed revision | 21 (document currently at 23) | |
Result | Has nits | |
Completed | 2013-11-21 |
review-ietf-sidr-origin-ops-21-secdir-lc-yu-2013-11-21-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 section appears to accurately document the significant limitations of Route Origin Authorizations. There should probably be an example of the sort of privilege escalation attacks that can result from incautious Local-Preference attributes. Editorial: In Section 4, "along with it's traffic engineering characteristic(s)", change "it's" to "its". Section 5 mentions a block 10.0.666.0/24, which is somewhat distracting because that is not a valid IPv4 address block.