RFC 7309: Redundancy Mechanism for Inter-domain VPLS Service
In plain English — editorial summary, not part of the RFC
In many existing Virtual Private LAN Service (VPLS) inter-domain deployments (based on RFC 4762), pseudowire (PW) connectivity offers no Provider Edge (PE) node redundancy, or offers PE node redundancy with only a single domain. This deployment approach incurs a high risk of service interruption, since at least one domain will not offer PE node redundancy. This document describes an inter-domain VPLS solution that provides PE node redundancy across domains.
Document record
- Document ID
- RFC7309
- Published
- July 2014
- Authors
- Z. Liu; L. Jin; R. Chen; D. Cai; S. Salam
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7275Inter-Chassis Communication Protocol for Layer 2 Virtual Private Network (L2VPN) Provider Edge (PE) RedundancyCurrent
June 2014
- RFC 7267Dynamic Placement of Multi-Segment PseudowiresCurrent
June 2014
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 7769Media Access Control (MAC) Address Withdrawal over Static PseudowireCurrent
February 2016
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 8469Recommendation to Use the Ethernet Control WordCurrent
November 2018
- RFC 5641Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status ValuesCurrent
August 2009
- RFC 5085Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for PseudowiresUpdated
December 2007
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?