Re: [bess] [Editorial Errata Reported] RFC9252 (7134)

[Chris Smiley <[e-mail]>]

Greetings Area Directors,

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/eid7134

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/cs

> On Sep 15, 2022, at 4:17 AM, RFC Errata System <[e-mail]> 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/eid7134
> 
> --------------------------------------
> Type: Editorial
> Reported by: Ketan Talaulikar <[e-mail]>
> 
> Section: 6.4
> 
> Original Text
> -------------
>                  +---------------------------------------+
>                  |  RD (8 octets)                        |
>                  +---------------------------------------+
>                  |  Ethernet Tag ID (4 octets)           |
>                  +---------------------------------------+
>                  |  IP Address Length (1 octet)          |
>                  +---------------------------------------+
>                  |  Originating Router's IP Address      |
>                  |          (4 or 16 octets)             |
>                  +---------------------------------------+
> 
>                        Figure 10: EVPN Route Type 4
> 
> 
> Corrected Text
> --------------
>                  +---------------------------------------+
>                  |  RD (8 octets)                        |
>                  +---------------------------------------+
>                  |Ethernet Segment Identifier (10 octets)|
>                  +---------------------------------------+
>                  |  IP Address Length (1 octet)          |
>                  +---------------------------------------+
>                  |  Originating Router's IP Address      |
>                  |          (4 or 16 octets)             |
>                  +---------------------------------------+
> 
>                        Figure 10: EVPN Route Type 4
> 
> 
> Notes
> -----
> The 2nd field in the figure should be "Ethernet Segment Identifier" of size 10 octets instead of the "Ethernet Tag ID" of size 4 octets.
> 
> RFC7432 is the EVPN specification for Ethernet Segment Route (Type 4) and hence the format in section 7.4 of RFC7432 is the correct one.
> RFC9252 has an error when showing the encoding format of this EVPN Route Type 4 as a reminder in Figure 10 in section 6.4. 
> 
> This is an editorial error.
> 
> 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
>