RFC 7275: Inter-Chassis Communication Protocol for Layer 2 Virtual Private Network (L2VPN) Provider Edge (PE) Redundancy
In plain English — editorial summary, not part of the RFC
This document specifies an Inter-Chassis Communication Protocol (ICCP) that enables Provider Edge (PE) device redundancy for Virtual Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS) applications. The protocol runs within a set of two or more PEs, forming a Redundancy Group, for the purpose of synchronizing data among the systems. It accommodates multi-chassis attachment circuit redundancy mechanisms as well as pseudowire redundancy mechanisms.
Document record
- Document ID
- RFC7275
- Published
- June 2014
- Authors
- L. Martini; S. Salam; A. Sajassi; M. Bocci; S. Matsushima; T. Nadeau
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 83
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7309Redundancy Mechanism for Inter-domain VPLS ServiceCurrent
July 2014
- RFC 7274Allocating and Retiring Special-Purpose MPLS LabelsUpdated
June 2014
- RFC 7271MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network OperatorsUpdated
June 2014
- RFC 7267Dynamic Placement of Multi-Segment PseudowiresCurrent
June 2014
- RFC 7260GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) ConfigurationCurrent
June 2014
- RFC 7257Virtual Private LAN Service (VPLS) Management Information BaseCurrent
July 2014
- RFC 7300Reservation of Last Autonomous System (AS) NumbersCurrent
July 2014
- RFC 7246Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table ContextUpdated
June 2014
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?