Last Call Review of draft-ietf-bess-bgp-srv6-args-05
review-ietf-bess-bgp-srv6-args-05-genart-lc-knodel-2025-02-21-00
| Request | Review of | draft-ietf-bess-bgp-srv6-args |
|---|---|---|
| Requested revision | No specific revision (document currently at 10) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2025-03-04 | |
| Requested | 2025-02-18 | |
| Authors | Ketan Talaulikar , Syed Kamran Raza , Jorge Rabadan , Wen Lin | |
| I-D last updated | 2025-07-19 (Latest revision 2025-05-09) | |
| Completed reviews |
Genart IETF Last Call review of -05
by Mallory Knodel
(diff)
Rtgdir Early review of -05 by Zheng Zhang (diff) Secdir IETF Last Call review of -06 by Mališa Vučinić (diff) Opsdir Telechat review of -06 by Joe Clarke (diff) |
|
| Assignment | Reviewer | Mallory Knodel |
| State | Completed | |
| Request | IETF Last Call review on draft-ietf-bess-bgp-srv6-args by General Area Review Team (Gen-ART) Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/gen-art/IfWBlTID2u4M8yH0deYSODTyZRo | |
| Reviewed revision | 05 (document currently at 10) | |
| Result | Ready | |
| Completed | 2025-02-21 |
review-ietf-bess-bgp-srv6-args-05-genart-lc-knodel-2025-02-21-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-bgp-srv6-args-?? Reviewer: Mallory Knodel Review Date: 2025-02-21 IETF LC End Date: 2025-03-04 IESG Telechat date: Not scheduled for a telechat Summary: This document updates recommendations "for the signaling and processing of SRv6 SID advertisements for BGP Service routes associated with SRv6 Endpoint Behaviors that support arguments" based on lessons learned from implementations of RFC9252. Major issues: None. Minor issues: It would perhaps help readers if in the introduction to the document that updates RFC9252, the authors quoted one seemingly critical passage, namely the description of the Transposition Scheme: This later form of encoding is referred to as the Transposition Scheme, where the SRv6 SID Structure Sub-Sub-TLV describes the sizes of the parts of the SRv6 SID and also indicates the offset of the variable part along with its length in the SRv6 SID value. The use of the Transposition Scheme is RECOMMENDED for the specific service encodings that allow it, as described ... This passage might then be modified in a clearer manner given the goals of the current document. Or perhaps this belongs in Section 4 on backwards compatibility. Nits/editorial comments: None. Well written and straight forward.