Last Call Review of draft-ietf-idr-bgp-ls-registry-04
review-ietf-idr-bgp-ls-registry-04-rtgdir-lc-vainshtein-2021-03-02-00

Request Review of draft-ietf-idr-bgp-ls-registry
Requested rev. no specific revision (document currently at 06)
Type Last Call Review
Team Routing Area Directorate (rtgdir)
Deadline 2021-03-16
Requested 2021-02-23
Requested by Alvaro Retana
Authors Adrian Farrel
Draft last updated 2021-03-02
Completed reviews Rtgdir Last Call review of -04 by Sasha Vainshtein (diff)
Genart Last Call review of -04 by Elwyn Davies (diff)
Assignment Reviewer Sasha Vainshtein 
State Completed
Review review-ietf-idr-bgp-ls-registry-04-rtgdir-lc-vainshtein-2021-03-02
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/UeVw-4sHYzjTaiA9N4qnSQA6TVk/
Reviewed rev. 04 (document currently at 06)
Review result Ready
Review completed: 2021-03-02

Review
review-ietf-idr-bgp-ls-registry-04-rtgdir-lc-vainshtein-2021-03-02

Hello,

I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.



Document: draft-ietf-idr-bgp-ls-registry-04

Reviewer: Alexander ("Sasha") Vainshtein

Review Date: 02-Mar-21

IETF LC End Date: 16-Mar-21

Intended Status: Standards Track



Summary: No issues found. This document is ready for publication.



Comments: The draft is quite short and very easy to read and understand.

The guidelines for the Designated Experts are quite straightforward and, IMHO, easy to follow.

I am not a security expert, but the type of attack described in the Security Considerations section ("excessive and bogus requests for code points") looks quite novel to me. I wonder if this type of attack has ever been observed before.



Major Issues: None found



Minor Issues: None found



Regards,

Sasha



Office: +972-39266302

Cell:      +972-549266302

Email:   Alexander.Vainshtein@rbbn.com



Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.