Last Call Review of draft-ietf-bess-pbb-evpn-isid-cmacflush-07
review-ietf-bess-pbb-evpn-isid-cmacflush-07-genart-lc-halpern-2023-06-30-00

Request Review of draft-ietf-bess-pbb-evpn-isid-cmacflush
Requested revision No specific revision (document currently at 09)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-07-11
Requested 2023-06-27
Authors Jorge Rabadan , Senthil Sathappan , Kiran Nagaraj , Masahiro Miyake , Taku Matsuda
I-D last updated 2024-03-20 (Latest revision 2023-10-23)
Completed reviews Secdir IETF Last Call review of -08 by Klaas Wierenga (diff)
Genart IETF Last Call review of -07 by Joel M. Halpern (diff)
Intdir Telechat review of -08 by Pascal Thubert (diff)
Rtgdir Early review of -04 by Russ White (diff)
Assignment Reviewer Joel M. Halpern
State Completed
Request IETF Last Call review on draft-ietf-bess-pbb-evpn-isid-cmacflush by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/CBzsxEwRDvcvkn70BvytwrKRLEg
Reviewed revision 07 (document currently at 09)
Result Ready w/nits
Completed 2023-06-30
review-ietf-bess-pbb-evpn-isid-cmacflush-07-genart-lc-halpern-2023-06-30-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-bess-pbb-evpn-isid-cmacflush-07
Reviewer: Joel Halpern
Review Date: 2023-06-30
IETF LC End Date: 2023-07-11
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed Standard.

reviewers note: My thanks to the authors / editors for a very helpful
introduction that made clear the problem to be solved.

Major issues: N/A

Minor issues:
    I got a bit confused in section 3, where the text says:
All the other fields are set and used as defined in [RFC7623]. This document
will refer to this route as the BMAC/I-SID route, as opposed to the [RFC7623]
BMAC/0 route (BMAC route sent with Ethernet Tag ID = 0).
    I got confused because when I went to RFC 7623, I could not find the string
    BMAC/0, and while I tried searching for related terms, I could not find
    what term is being distinguished.  The string BMAC does not occur in RFC
    7623.  So this and later (e.g. 4.1) references to 7623 use of BMAC/0 is
    confusing.

Nits/editorial comments: N/A