Top posting for the attention of our new AD :-)
On Tue, Feb 20, 2024 at 10:18 PM RFC Errata System < rfc-edi...@rfc-editor.org> wrote: > The following errata report has been submitted for RFC9252, > "BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7817 > > -------------------------------------- > Type: Technical > Reported by: Ketan Talaulikar <ketant.i...@gmail.com> > > Section: 3.2.1 > > Original Text > ------------- > As defined in [RFC8986], the sum of the Locator Block Length (LBL), > Locator Node Length (LNL), Function Length (FL), and Argument Length > (AL) fields MUST be less than or equal to 128 and greater than the > sum of Transposition Offset and Transposition Length. > > Corrected Text > -------------- > As defined in [RFC8986], the sum of the Locator Block Length (LBL), > Locator Node Length (LNL), Function Length (FL), and Argument Length > (AL) fields MUST be less than or equal to 128 and greater than or > equal to the sum of Transposition Offset and Transposition Length. > > Notes > ----- > The sum of Trans Off and Trans Length can be equal to the LBL+LNL+FL+AL > when the last part of the SID (function or argument) is getting transposed. > > This is clear also from the example below in the next paragraph of the > same section: > > As an example, consider that the sum of the Locator Block and the > Locator Node parts is 64. For an SRv6 SID where the entire Function > part of size 16 bits is transposed, the transposition offset is set > to 64 and the transposition length is set to 16. While for an SRv6 > SID for which the FL is 24 bits and only the lower order 20 bits are > transposed (e.g., due to the limit of the MPLS Label field size), the > transposition offset is set to 68 and the transposition length is set > to 20. > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC9252 (draft-ietf-bess-srv6-services-15) > -------------------------------------- > Title : BGP Overlay Services Based on Segment Routing over > IPv6 (SRv6) > Publication Date : July 2022 > Author(s) : G. Dawra, Ed., K. Talaulikar, Ed., R. Raszuk, B. > Decraene, S. Zhuang, J. Rabadan > Category : PROPOSED STANDARD > Source : BGP Enabled ServiceS > Area : Routing > Stream : IETF > Verifying Party : IESG >
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
