The following errata report has been held for document update for RFC8214, "Virtual Private Wire Service Support in Ethernet VPN".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7837 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Alexander ("Sasha") Vainshtein <alexander.vainsht...@rbbn.com> Date Reported: 2024-03-05 Held by: John Scudder (IESG) Section: 3.1 Original Text ------------- 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. Corrected Text -------------- 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/ -------------------------------------- RFC8214 (draft-ietf-bess-evpn-vpws-14) -------------------------------------- Title : Virtual Private Wire Service Support in Ethernet VPN Publication Date : August 2017 Author(s) : S. Boutros, A. Sajassi, S. Salam, J. Drake, J. Rabadan Category : PROPOSED STANDARD Source : BGP Enabled ServiceS Area : Routing Stream : IETF Verifying Party : IESG _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
