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/eid8375 -------------------------------------- Type: Technical Reported by: Alexander ("Sasha") Vainshtein <alexander.vainsht...@rbbn.com> Section: 6.3 Original Text ------------- The ingress PE gets the destination TS's MAC address for that TS's IP address from its ARP table or NDP cache. It encapsulates the packet with that destination MAC address and a source MAC address corresponding to that IRB interface and sends the packet to its destination subnet MAC-VRF/BT. Corrected Text -------------- The ingress PE gets the destination TS's MAC address for that TS's IP address from its ARP table or NDP cache. It encapsulates the packet with that destination MAC address and a source MAC address corresponding to that IRB interface. In addition, if the following conditions for the EVPN instance in question are met: - uses MPLS encapsulation - implements VLAN-aware bundle service interface as defined in Section 6.3 of RFC 7432 then the VLAN tag with the "normalized VID" of the corresponding BT is pushed on the customer IP packet. The resulting packet is sent to its destination subnet MAC-VRF/BT. Notes ----- Section 6.3 of RFC 743 OPTIONALLY allows a MAC-VRF that implements VLAN-aware bundle service interface and uses MPLS encapsulation to advertise the same label for all its broadcast domains. This option is only allowed when each broadcast domain in such a MAC-VRF is represented by the same VID in all the PEs. With this option, a VLAN tag with the "normalized" VID of the specific ingress domain MUST be present when the packet crosses the underlay, and MUST be used for identification of the specific broadcast domain in the egress PE. In the case of inter-subnet forwarding, the original VLAN tag of IP packets undergoing such forwarding does not identify the broadcast domain to which the packet would be sent. 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. -------------------------------------- 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 Stream : IETF Verifying Party : IESG _______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
