[bess] [Errata Held for Document Update] RFC8214 (7562)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 30 October 2024 13:42 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
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 E4566C14F699; Wed, 30 Oct 2024 06:42:37 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 5DE087F9E0; Wed, 30 Oct 2024 06:42:37 -0700 (PDT)
To: alexander.vainshtein@rbbn.com, sboutros@vmware.com, sajassi@cisco.com, ssalam@cisco.com, jdrake@juniper.net, jorge.rabadan@nokia.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20241030134237.5DE087F9E0@rfcpa.rfc-editor.org>
Date: Wed, 30 Oct 2024 06:42:37 -0700
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: ET4J6WJPLONGOWEJ7WYG3YTK7MDK4LII
X-Message-ID-Hash: ET4J6WJPLONGOWEJ7WYG3YTK7MDK4LII
X-Mailman-Approved-At: Wed, 30 Oct 2024 06:50:07 -0700
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] RFC8214 (7562)
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/5SSi_ByBEjr6V510w_K2_SFDF_o>
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 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 <alexander.vainshtein@rbbn.com>
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