RFC 8214: Virtual Private Wire Service Support in Ethernet VPN
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8214
- Published
- August 2017
- Authors
- S. Boutros; A. Sajassi; S. Salam; J. Drake; J. Rabadan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8211Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI)Current
September 2017
- RFC 8218Multipath Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
August 2017
- RFC 8210The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1Current
September 2017
- RFC 8209A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification RequestsCurrent
September 2017
- RFC 8208BGPsec Algorithms, Key Formats, and Signature FormatsObsoleted
September 2017
- RFC 8220Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)Current
September 2017
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8206BGPsec Considerations for Autonomous System (AS) MigrationCurrent
September 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?