Last Call Review of draft-ietf-grow-large-communities-usage-06
review-ietf-grow-large-communities-usage-06-secdir-lc-wierenga-2017-04-27-00
Request | Review of | draft-ietf-grow-large-communities-usage |
---|---|---|
Requested revision | No specific revision (document currently at 07) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2017-04-21 | |
Requested | 2017-04-07 | |
Authors | Job Snijders , John Heasley , Martijn Schmidt | |
I-D last updated | 2017-04-27 | |
Completed reviews |
Rtgdir Last Call review of -06
by Martin Vigoureux
(diff)
Opsdir Last Call review of -07 by Jouni Korhonen Genart Last Call review of -06 by Stewart Bryant (diff) Genart Telechat review of -07 by Stewart Bryant Secdir Last Call review of -06 by Klaas Wierenga (diff) |
|
Assignment | Reviewer | Klaas Wierenga |
State | Completed | |
Request | Last Call review on draft-ietf-grow-large-communities-usage by Security Area Directorate Assigned | |
Reviewed revision | 06 (document currently at 07) | |
Result | Has nits | |
Completed | 2017-04-27 |
review-ietf-grow-large-communities-usage-06-secdir-lc-wierenga-2017-04-27-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 presents examples of how operators may use BGP large communities to support some typical use-cases. In general the document is well written and I have no major issues, and I consider it: ready with nits (see below) My one nit is that even though I think that the statement in the security considerations "Operators should note the recommendations in Section 11(https://tools.ietf.org/html/draft-ietf-grow-large-communities-usage-06#section-11) of BGP Operations and Security [RFC7454(https://tools.ietf.org/html/rfc7454)]” is largely true, it would be useful if the authors would expand a little on that, not being an expert in this field, I am wondering if the use-cases you describe in one way or the other influence the RFC7454 considerations. Klaas