The following errata report has been submitted 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

--------------------------------------
Type: Technical
Reported by: Alexander ("Sasha") Vainshtein <alexander.vainsht...@rbbn.com>

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.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
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

Reply via email to