Virtual Private Wire Service Support in Ethernet VPN
RFC 8214
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2022-05-27
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2021-04-06
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2021-02-09
|
(System) | Received changes through RFC Editor sync (removed Errata tag (all errata rejected)) |
|
2019-11-20
|
Alvaro Retana | Downref to RFC 7348 approved by Last Call for rfc8214-14 |
|
2018-12-11
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2017-08-24
|
(System) | IANA registries were updated to include RFC8214 |
|
2017-08-23
|
(System) | Received changes through RFC Editor sync (created alias RFC 8214, changed title to 'Virtual Private Wire Service Support in Ethernet VPN', changed abstract to … Received changes through RFC Editor sync (created alias RFC 8214, changed title to 'Virtual Private Wire Service Support in Ethernet VPN', changed abstract to 'This document describes how Ethernet VPN (EVPN) can be used to support the Virtual Private Wire Service (VPWS) in MPLS/IP networks. EVPN accomplishes the following for VPWS: provides Single-Active as well as All-Active multihoming with flow-based load-balancing, eliminates the need for Pseudowire (PW) signaling, and provides fast protection convergence upon node or link failure.', changed pages to 17, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-08-23, changed IESG state to RFC Published) |
|
2017-08-23
|
(System) | RFC published |