[bess] [Errata Held for Document Update] RFC9062 (8044)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 10 February 2025 10:42 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from mail.ietf.org (ietfa.amsl.com [50.223.129.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 5A239C139C65; Mon, 10 Feb 2025 02:42:05 -0800 (PST)
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479BBC1D8D63; Mon, 10 Feb 2025 02:42:05 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id B18FD21AD5E; Mon, 10 Feb 2025 02:42:04 -0800 (PST)
To: alexander.vainshtein@rbbn.com, ssalam@cisco.com, sajassi@cisco.com, aldrin.ietf@gmail.com, jdrake@juniper.net, d3e3e3@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250210104204.B18FD21AD5E@rfcpa.rfc-editor.org>
Date: Mon, 10 Feb 2025 02:42:04 -0800
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Hits: max-recipients
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-size; news-moderation; no-subject; digests; suspicious-header
Message-ID-Hash: OCB2RWX7DWGG6POZPBOMXZVFMULYMALO
X-Message-ID-Hash: OCB2RWX7DWGG6POZPBOMXZVFMULYMALO
X-Mailman-Approved-At: Mon, 10 Feb 2025 04:46:42 -0800
CC: gunter.van_de_velde@nokia.com, iesg@ietf.org, bess@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [bess] [Errata Held for Document Update] RFC9062 (8044)
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/ErNBVgk9WUPMGDCddtSHm60KPBc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>
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.vainshtein@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] [Errata Held for Document Update] RFC9062 … RFC Errata System