RFC 7795: Pseudowire Redundancy on the Switching Provider Edge (S-PE)
In plain English — editorial summary, not part of the RFC
This document describes Multi-Segment Pseudowire (MS-PW) protection scenarios in which pseudowire redundancy is provided on the Switching Provider Edge (S-PE) as defined in RFC 5659. Operations of the S-PEs that provide PW redundancy are specified in this document. Signaling of the Preferential Forwarding status as defined in RFCs 6870 and 6478 is reused. This document does not require any change to the Terminating Provider Edges (T-PEs) of MS-PW.
Document record
- Document ID
- RFC7795
- Published
- February 2016
- Authors
- J. Dong; H. Wang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7796Ethernet-Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)Current
March 2016
- RFC 7794IS-IS Prefix Attributes for Extended IPv4 and IPv6 ReachabilityCurrent
March 2016
- RFC 7792RSVP-TE Signaling Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
March 2016
- RFC 7784Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIBCurrent
February 2016
- RFC 7783Coordinated Multicast Trees (CMT) for Transparent Interconnection of Lots of Links (TRILL)Current
February 2016
- RFC 7782Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC AttachmentsCurrent
February 2016
- RFC 7781Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active AccessCurrent
February 2016
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
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?