Last Call Review of draft-ietf-idr-deprecate-30-31-129-00
review-ietf-idr-deprecate-30-31-129-00-secdir-lc-perlman-2016-12-22-00
| Request | Review of | draft-ietf-idr-deprecate-30-31-129 |
|---|---|---|
| Requested revision | No specific revision (document currently at 02) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2016-12-16 | |
| Requested | 2016-12-02 | |
| Authors | Job Snijders | |
| Draft last updated | 2016-12-22 | |
| Completed reviews |
Opsdir Telechat review of -02
by
Mehmet Ersue
Genart Last Call review of -00 by Meral Shirazipour (diff) Secdir Last Call review of -00 by Radia Perlman (diff) Genart Telechat review of -02 by Meral Shirazipour |
|
| Assignment | Reviewer | Radia Perlman |
| State | Completed | |
| Review |
review-ietf-idr-deprecate-30-31-129-00-secdir-lc-perlman-2016-12-22
|
|
| Reviewed revision | 00 (document currently at 02) | |
| Result | Ready | |
| Completed | 2016-12-22 |
review-ietf-idr-deprecate-30-31-129-00-secdir-lc-perlman-2016-12-22-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 very brief document simply notes that people have been using unassigned BGP path attribute values, and thus "Per this document, IANA has marked the BGP Path Attributes registry entries for values 30, 31, 129 as "deprecated"." As the document correctly states, there are no security considerations for this. Radia