The following errata report has been held for document update for RFC9062, "Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8044 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Alexander ("Sasha") Vainshtein <alexander.vainsht...@rbbn.com> Date Reported: 2024-07-23 Held by: Gunter Van de Velde (IESG) Section: 2.3 Original Text ------------- EVPN allows for three different models of unicast label assignment: label per EVI, label per <ESI, Ethernet Tag>, and label per MAC address. Corrected Text -------------- EVPN allows for four different models of unicast label assignment: * label per EVI * label per <EVI, Ethernet Tag> * label per <ESI, Ethernet Tag> * label per MAC address. Notes ----- Section 9.1.1 of RFC 7432 defines four label allocation models for labels advertised in the Label1 field of MAC/IP Advertisement (EVPN Type 2 routes). One of these models is missing in the original text f the RFC. -------------------------------------- RFC9062 (draft-ietf-bess-evpn-oam-req-frmwk-10) -------------------------------------- Title : Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM) Publication Date : June 2021 Author(s) : S. Salam, A. Sajassi, S. Aldrin, J. Drake, D. Eastlake 3rd Category : INFORMATIONAL Source : BGP Enabled ServiceS Stream : IETF Verifying Party : IESG _______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
