Re: [bess] [Editorial Errata Reported] RFC9135 (7683)

[Rebecca VanRheenen <[e-mail]>]

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

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 Oct 19, 2023, at 12:56 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC9135,
> "Integrated Routing and Bridging in Ethernet VPN (EVPN)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7683
> 
> --------------------------------------
> Type: Editorial
> Reported by: Denis Vrkic <[e-mail]>
> 
> Section: 4.2.
> 
> Original Text
> -------------
>  2.  However, if PE2 is configured for asymmetric IRB mode, PE2 will
>       advertise TS4 MAC/IP information in a MAC/IP Advertisement route
>       with a zero Label2 field and no Route Target identifying IP-VRF1.
>       In this case, PE2 will install TS4 information in its ARP table
>       and BT1.  When a packet from TS2 to TS4 arrives at PE1, a longest
>       prefix match on IP-VRF1's route table will yield the local IRB
>       interface to BT1, where a subsequent ARP and bridge table lookup
>       will provide the information for an asymmetric forwarding mode to
>       PE2.
> 
> Corrected Text
> --------------
>  2.  However, if PE2 is configured for asymmetric IRB mode, PE2 will
>       advertise TS4 MAC/IP information in a MAC/IP Advertisement route
>       with a zero Label2 field and no Route Target identifying IP-VRF1.
>       In this case, PE1 will install TS4 information in its ARP table
>       and BT1.  When a packet from TS2 to TS4 arrives at PE1, a longest
>       prefix match on IP-VRF1's route table will yield the local IRB
>       interface to BT1, where a subsequent ARP and bridge table lookup
>       will provide the information for an asymmetric forwarding mode to
>       PE2.
> 
> Notes
> -----
> PE1 will use ARP table for forwarding traffic to PE2 - seems like typo
> 
> 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. 
> 
> --------------------------------------
> RFC9135 (draft-ietf-bess-evpn-inter-subnet-forwarding-15)
> --------------------------------------
> Title               : Integrated Routing and Bridging in Ethernet VPN (EVPN)
> Publication Date    : October 2021
> Author(s)           : A. Sajassi, S. Salam, S. Thoria, J. Drake, J. Rabadan
> Category            : PROPOSED STANDARD
> Source              : BGP Enabled ServiceS
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
>