RFC 8365, "A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)", March 2018

Errata ID: 7735
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Gaurav Sinha
Date Reported: 2023-12-19
Rejected by: John Scudder
Date Rejected: 2024-02-12

Section 8.3.1 says:

Since VXLAN and NVGRE encapsulations do not include the ESI label, 
other means of performing the split-horizon filtering function must 
be devised for these encapsulations.

It should say:

The "ESI Label" field, in the "ESI Label" Extended Community, is set 
to all zeros in case of VxLAN encapsulation. Since even though the 
VXLAN and NVGRE encapsulations send the "ESI Label" Extended Community, 
yet they do not set the "ESI label" field in it. Therefore, other means 
of performing the split-horizon filtering function must be devised for 
these encapsulations.

Notes:

It should be mentioned somewhere in this RFC document that the "ESI Label" Extended Community is sent with VxLAN encapsulation too, just like it is used with MPLS, but with the "MPLS Label" field set to all zeros in case of VxLAN.

Otherwise, it gives rise to the unanswered question in mind, about the value of that field, given that there are no labels in VxLAN.
--VERIFIER NOTES--
This change appears to be unneeded in this document, see https://mailarchive.ietf.org/arch/msg/bess/ztIEqCJh23KdAbEaec-zeQBwdSs/

Related (and mentioned in the referenced email thread) rfc7432bis does clarify the situation with the note, "The ESI label value MAY be zero if no split-horizon filtering procedures are required in any of the VLANs of the Ethernet Segment. This is the case in [RFC8214]".

Report New Errata