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/eid7562 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Alexander ("Sasha") Vainshtein <[email protected]> Date Reported: 2023-07-13 Held by: Gunter Van de Velde (IESG) Section: 3.1 Original Text ------------- In a multihoming All-Active scenario, there is no Designated Forwarder (DF) election, and all the PEs in the ES that are active and ready to forward traffic to/from the CE will set the P Flag. Corrected Text -------------- In a multihoming All-Active scenario, there is no Designated Forwarder (DF) election, and all the PEs in the ES that are active and ready to forward traffic to/from the CE SHOULD set the P Flag. Notes ----- The original text in the RFC does not express any requirement level ("will" is not a recognized IETF term for expressing requirement levels as defined in RFC 2119). The new test replaces "will" with "SHOULD". SHOULD and not MUST is proposed to avoid potential issues with implementations that did not set P flag in the L2 Attributes Extended Community in All-Active multi-homing scenarios (since this was not required) and would suddenly become non-compliant if the text were changed to from "will" to MUST. -------------------------------------- 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 Stream : IETF Verifying Party : IESG _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
