Any update on this?

On Thu, Nov 9, 2023 at 12:03 AM Rebecca VanRheenen <rvanrhee...@amsl.com>
wrote:

> HI Andrew,
>
> We are unable to verify this erratum that the submitter marked as
> editorial.
> Please note that we have changed the “Type” of the following errata
> report to “Technical”.  As Stream Approver, please review and set the
> Status and Type accordingly (see the definitions at
> https://www.rfc-editor.org/errata-definitions/).
>
> You may review the report at:
> https://www.rfc-editor.org/errata/eid7652
>
> Please see https://www.rfc-editor.org/how-to-verify/ for further
> information on how to verify errata reports.
>
> Further information on errata can be found at:
> https://www.rfc-editor.org/errata.php.
>
> Thank you.
>
> RFC Editor/rv
>
>
>
> > On Sep 22, 2023, at 1:05 AM, 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/eid7652
> >
> > --------------------------------------
> > Type: Editorial
> > Reported by: Ketan Talaulikar <ketant.i...@gmail.com>
> >
> > Section: 3.2.1
> >
> > Original Text
> > -------------
> >   Transposition Offset indicates the bit position, and Transposition
> >   Length indicates the number of bits that are being taken out of the
> >   SRv6 SID value and encoded in the MPLS Label field.  The bits that
> >   have been shifted out MUST be set to 0 in the SID value.
> >
> > Corrected Text
> > --------------
> >   Transposition Offset indicates the bit position and Transposition
> >   Length indicates the number of bits that are being taken out of the
> >   SRv6 SID value and put into high order bits of MPLS label field. The
> >   bits that have been shifted out MUST be set to 0 in the SID value.
> >
> > Notes
> > -----
> > This errata reverses an editorial change that was made during the AUTH48
> phase and restores the text that came from the WG and IESG review. Refer
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services-15#page-10
> >
> > This change was made during the AUTH48 since the "high order bits" was
> already covered under various subsections of Sec 6. However, readers have
> reported that there are other places in Sec 6 and Sec 5 where transposition
> also occurs and that the original text was still required.
> >
> > Instructions:
> > -------------
> > This erratum is currently posted as "Reported". If necessary, please
> > use "Reply All" to discuss whether it should be verified or
> > rejected. When a decision is reached, the verifying party
> > can 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

Reply via email to