RFC 9135, "Integrated Routing and Bridging in Ethernet VPN (EVPN)", October 2021

Errata ID: 7686
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Denis Vrkic
Date Reported: 2023-10-20
Rejected by: John Scudder
Date Rejected: 2024-02-12

Section 6.1 says:

6.1.  Control Plane - Advertising PE

   When a PE (e.g., PE1 in Figure 4 above) learns the MAC and IP address
   of an attached TS (e.g., via an ARP request or ND Neighbor
   Solicitation), it populates its MAC-VRF/BT, IP-VRF, and ARP table or
   NDP cache just as in the case for symmetric IRB.

It should say:

6.1.  Control Plane - Advertising PE

   When a PE (e.g., PE1 in Figure 4 above) learns the MAC and IP address
   of an attached TS (e.g., via an ARP request or ND Neighbor
   Solicitation), it populates its MAC-VRF/BT and ARP table or
   NDP cache.

Notes:

- advertising PE (egress PE) is not advertising Label2 ("the MPLS Label2 field MUST NOT be included in this route.")
- so this must be asymmetric egress PE
- in 4.2 is stated that: "the asymmetric IRB mode simplifies the forwarding model
and saves space in the IP-VRF route table, since host routes are not installed in the route table."
- so i guess that, advertising PE in asymmetric mode, is NOT leaning/storing local IP to IP-VRF table only ARP (bound to IP-VRF) and MAC into MAC-VRF
--VERIFIER NOTES--
See https://mailarchive.ietf.org/arch/msg/bess/9pvIR6OysyFKso9rDRb-CJj7we8/

Report New Errata