The following errata report has been verified for RFC8214,
"Virtual Private Wire Service Support in Ethernet VPN". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6743

--------------------------------------
Status: Verified
Type: Technical

Reported by: Adrian Farrel <[email protected]>
Date Reported: 2021-11-19
Verified by: Andrew Alston (IESG)

Section: 4

Original Text
-------------
          Ethernet                                          Ethernet
          Native   |<--------- EVPN Instance ----------->|  Native
          Service  |                                     |  Service
          (AC)     |     |<-PSN1->|       |<-PSN2->|     |  (AC)
             |     V     V        V       V        V     V  |
             |     +-----+      +-----+  +-----+   +-----+  |
      +----+ |     | PE1 |======|ASBR1|==|ASBR2|===| PE3 |  |    +----+
      |    |-------+-----+      +-----+  +-----+   +-----+-------|    |
      | CE1| |                                              |    |CE2 |
      |    |-------+-----+      +-----+  +-----+   +-----+-------|    |
      +----+ |     | PE2 |======|ASBR3|==|ASBR4|===| PE4 |  |    +----+
           ^       +-----+      +-----+  +-----+   +-----+          ^
           |   Provider Edge 1        ^        Provider Edge 2      |
           |                          |                             |
           |                          |                             |
           |              EVPN Inter-provider point                 |
           |                                                        |
           |<---------------- Emulated Service -------------------->|

                   Figure 3: EVPN-VPWS Deployment Model


Corrected Text
--------------
          Ethernet                                          Ethernet
          Native   |<--------- EVPN Instance ----------->|  Native
          Service  |                                     |  Service
          (AC)     |     |<-PSN1->|       |<-PSN2->|     |  (AC)
             |     V     V        V       V        V     V  |
             |     +-----+      +-----+  +-----+   +-----+  |
      +----+ |     | PE1 |======|ASBR1|==|ASBR2|===| PE3 |  |    +----+
      |    |-------+-----+      +-----+  +-----+   +-----+-------|    |
      | CE1| |                                              |    |CE2 |
      |    |-------+-----+      +-----+  +-----+   +-----+-------|    |
      +----+ |     | PE2 |======|ASBR3|==|ASBR4|===| PE4 |  |    +----+
           ^       +-----+      +-----+  +-----+   +-----+       ^
           |   Provider Edge 1        ^        Provider Edge 2   |
           |                          |                          |
           |                          |                          |
           |              EVPN Inter-provider point              |
           |                                                     |
           |<---------------- Emulated Service ----------------->|

                   Figure 3: EVPN-VPWS Deployment Model


Notes
-----
The right-hand end of the Emulated Service should be aligned with the 
provider-facing AC port on CE2 and not  placed in the middle of CE2.
Although this may appear to be a minor editorial issue, the technical 
consequences are significant.

--------------------------------------
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
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to