Last Call Review of draft-ietf-mpls-deprecate-bgp-entropy-label-01
review-ietf-mpls-deprecate-bgp-entropy-label-01-secdir-lc-kelly-2014-10-30-00
| Request | Review of | draft-ietf-mpls-deprecate-bgp-entropy-label |
|---|---|---|
| Requested rev. | no specific revision (document currently at 02) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2014-11-03 | |
| Requested | 2014-10-23 | |
| Authors | John Scudder, Kireeti Kompella | |
| Draft last updated | 2014-10-30 | |
| Completed reviews |
Genart Last Call review of -01 by Ben Campbell
(diff)
Secdir Last Call review of -01 by Scott Kelly (diff) |
|
| Assignment | Reviewer | Scott Kelly |
| State | Completed | |
| Review | review-ietf-mpls-deprecate-bgp-entropy-label-01-secdir-lc-kelly-2014-10-30 | |
| Reviewed rev. | 01 (document currently at 02) | |
| Review result | Ready | |
| Review completed: | 2014-10-30 |
Review
review-ietf-mpls-deprecate-bgp-entropy-label-01-secdir-lc-kelly-2014-10-30
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 draft deprecates a BGP attribute. The security considerations section says that attacks on the attribute require the attacker to be part of the control plane, where they can do many other things, and this is not significantly changed by deprecating the attribute (actually, it doesn’t say precisely that, but I think that’s what it implies). I’m not a routing expert, but that sounds right to me. I see no issues with this draft. —Scott