Early Review of draft-ietf-idr-bgp-optimal-route-reflection-21
review-ietf-idr-bgp-optimal-route-reflection-21-secdir-early-dunbar-2020-12-15-00
Request | Review of | draft-ietf-idr-bgp-optimal-route-reflection-21 |
---|---|---|
Requested revision | 21 (document currently at 28) | |
Type | Early Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2020-12-07 | |
Requested | 2020-11-12 | |
Requested by | Susan Hares | |
Authors | Robert Raszuk , Bruno Decraene , Christian Cassar , Erik Aman , Kevin Wang | |
I-D last updated | 2020-12-15 | |
Completed reviews |
Rtgdir Early review of -11
by Daniele Ceccarelli
(diff)
Secdir Early review of -21 by Linda Dunbar (diff) Opsdir Early review of -21 by Dan Romascanu (diff) Rtgdir Early review of -21 by Daniele Ceccarelli (diff) |
|
Assignment | Reviewer | Linda Dunbar |
State | Completed | |
Request | Early review on draft-ietf-idr-bgp-optimal-route-reflection by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/g9lBnPoeNPuQE2jwvkyP6dtMsSQ | |
Reviewed revision | 21 (document currently at 28) | |
Result | Has nits | |
Completed | 2020-12-15 |
review-ietf-idr-bgp-optimal-route-reflection-21-secdir-early-dunbar-2020-12-15-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 alters how BGP Route Reflector computes the optimal routes on behalf of clients. Instead using its own IGP cost to the AS Exit points, the document describes the steps for RR to compute the optimal route by using Clients' position to the AS Exit points. The described method is useful when RR is centralized. For deployment with distributed RR closer to the clients, the described method doesn't have any benefits. Security Concern: If RR's information of its clients topology is compromised, then the optimal paths selected by the RR might not be accurate anymore. Minor nits: Page 7: Section 3.2. "If the routing routing optimization requires ..." Is it a typo? duplicated word "routing"? Last sentence: "This needed for use cases ..." Do you mean "This is needed for use cases ..." Cheers, Linda Dunbar