Thanks, Ali.
By the way, 7432bis has expired. Please consider refreshing it.
—John
> On Feb 11, 2024, at 2:49 PM, Ali Sajassi (sajassi) wrote:
>
> Hi John,
> RFC8365 relies heavily on base MPLS-EVPN RFC (i.e., RFC7432/RFC7432bis) and
> assumes the reader is very familiar with
Hi John,
RFC8365 relies heavily on base MPLS-EVPN RFC (i.e., RFC7432/RFC7432bis) and
assumes the reader is very familiar with RFC7432/7432bis. ESI label as
described in RFC7432/RFC7432bis is used for split-horizon filtering; however,
VxLAN-EVPN (RFC8365) doesn’t use split-horizon filtering
Hi All,
I started to look at this and pretty quickly got lost in a maze of twisty
passages. RFC 8365 doesn’t mention the "ESI Label" Extended Community at all, I
suppose it gets dragged in through the reliance on RFC 7432 as an underlying
mechanism. Since the erratum proposes a new requirement
Hi John,
RFC8365 relies heavily on base MPLS-EVPN RFC (i.e., RFC7432/RFC7432bis) and
assumes the reader is very familiar with RFC7432/7432bis. ESI label as
described in RFC7432/RFC7432bis is used for split-horizon filtering; however,
VxLAN-EVPN (RFC8365) doesn’t use split-horizon filtering but
