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/eid8478 -------------------------------------- Type: Technical Reported by: Alexander ("Sasha") Vainshtein <[email protected]> Section: 3 Original Text ------------- IP-VRF is identified by its corresponding Route Target and Route Distinguisher, and MAC-VRF is also identified by its corresponding Route Target and Route Distinguisher. If operating in EVPN VLAN-based mode, then a receiving PE that receives an EVPN route with a MAC-VRF Route Target can identify the corresponding bridge table; however, if operating in EVPN VLAN-aware bundle mode, then the receiving PE needs both the MAC-VRF Route Target and VLAN ID in order to identify the corresponding bridge table. Corrected Text -------------- IP-VRF is identified by its corresponding Route Target and Route Distinguisher, and MAC-VRF is also identified by its corresponding Route Target and Route Distinguisher. If operating in EVPN VLAN-based mode, then a receiving PE that receives an EVPN route with a MAC-VRF Route Target can identify the corresponding bridge table; however, if operating in EVPN VLAN-aware bundle mode, then the receiving PE needs both the MAC-VRF Route Target and Ethernet Tag ID in the NLRI of the route in order to identify the corresponding bridge table. Notes ----- MAC/IP Advertisement (EVPN Type 2) routes for IP-->MAC pairs do not carry any information about VLAN IDs used in encapsulation of ARP (or NA) messages that trigger their advertisement. Instead, they carry Ethernet Tag IDs of Broadcast Domains in which these messages have been received which may represent the original VLAN ID or the so-called "normalized" VLAN ID of the Broadcast Domain as defined in Section 6.3 of RFC 7432. 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 -- [email protected] To unsubscribe send an email to [email protected]
