RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 8214, "Virtual Private Wire Service Support in Ethernet VPN", August 2017

Source of RFC: bess (rtg)

Errata ID: 6117
Status: Rejected
Type: Technical
Publication Format(s) : TEXT

Reported By: Luc Andre Burdet
Date Reported: 2020-04-22
Rejected by: Martin Vigourex
Date Rejected: 2021-02-08

Section 3.1, 8 says:

3.1.  EVPN Layer 2 Attributes Extended Community
            0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           |   MBZ                   |C|P|B|  (MBZ = MUST Be Zero)
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         Name     Meaning
         ---------------------------------------------------------------
         P        If set to 1 in multihoming Single-Active scenarios, ...
         B        If set to 1 in multihoming Single-Active scenarios, ...
         C        If set to 1, a control word [RFC4448] MUST be present ...

8.  IANA Considerations
   Initial registrations are as follows:

        P      Advertising PE is the primary PE.
        B      Advertising PE is the backup PE.
        C      Control word [RFC4448] MUST be present.


It should say:

Option 1 : change explicit bitfield
==========
3.1.  EVPN Layer 2 Attributes Extended Community
            0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
##<swap>   |   MBZ                   |C|B|P|  (MBZ = MUST Be Zero)
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         Name     Meaning
         ---------------------------------------------------------------
         P        If set to 1 in multihoming Single-Active scenarios, ...
         B        If set to 1 in multihoming Single-Active scenarios, ...
         C        If set to 1, a control word [RFC4448] MUST be present ...

8.  IANA Considerations
   Initial registrations are as follows:

        P      Advertising PE is the primary PE.
        B      Advertising PE is the backup PE.
        C      Control word [RFC4448] MUST be present.


Option 2 : change implicit order
==========
3.1.  EVPN Layer 2 Attributes Extended Community
            0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           |   MBZ                   |C|P|B|  (MBZ = MUST Be Zero)
           +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
         Name     Meaning
         ---------------------------------------------------------------
##       B        If set to 1 in multihoming Single-Active scenarios, ...
##<swap 'implicit' list order B,P to match bitfield>
##       P        If set to 1 in multihoming Single-Active scenarios, ...
         C        If set to 1, a control word [RFC4448] MUST be present ...

8.  IANA Considerations
   Initial registrations are as follows:

##      B      Advertising PE is the backup PE.
##<swap 'implicit' list order B,P to match bitfield>
##      P      Advertising PE is the primary PE.
        C      Control word [RFC4448] MUST be present.




Notes:

While technically section 8 is not requesting any bit-position from IANA registry, the ordering of requests P-B-C vs. the field definition B-P-C is confusing, or at least inconsistent.

A clarifying statement is required:
- the field definition is should be swapped; or
- the field definition shall prime over all the places implying order when listing P-B-C
--VERIFIER NOTES--
This is not a technical errata or at least the reasonable solution to it seems to be editorial (shifting text around) rather than modifying the order of bits on the wire.

Report New Errata



Advanced Search