RFC 8214, "Virtual Private Wire Service Support in Ethernet VPN", August 2017

Errata ID: 7837
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alexander ("Sasha") Vainshtein
Date Reported: 2024-03-05
Held for Document Update by: John Scudder
Date Held: 2024-03-07

Section 3.1 says:

This document defines a new extended community [RFC4360], to be included with per-EVI Ethernet A-D routes.  This attribute is mandatory if multihoming is enabled.

It should say:

This document defines a new extended community [RFC4360], to be included with per-EVI Ethernet A-D routes.  

If multihoming is enabled, this attribute is MANDATORY regardless of whether the per-EVI Ethernet A-D route is advertised by an EVPN-VPWS instance or by a "bridging" EVPN instance.

Notes:

The lower-case "mandatory" used in the original text does not represent any form of requirement in IETF documents, therefore replacing with upper-case "MANDATORY" is needed.

The reference to per-EVI Ethernet A-D routes advertised by both "bridging" EVPN and EVPN-VPWS is needed to remove possible doubts about the scope of this requirement since the standard is about EVPN-VPWS.

--
Verifier note: see also https://mailarchive.ietf.org/arch/msg/bess/vBYU98CJkLvHfvnX_6wIsV2cCFM/

Report New Errata