RFC 6478: Pseudowire Status for Static Pseudowires
In plain English — editorial summary, not part of the RFC
This document specifies a mechanism to signal Pseudowire (PW) status messages using a PW associated channel (ACh). Such a mechanism is suitable for use where no PW dynamic control plane exits, known as static PWs, or where a Terminating Provider Edge (T-PE) needs to send a PW status message directly to a far-end T-PE. The mechanism allows PW Operations, Administration, and Maintenance (OAM) message mapping and PW redundancy to operate on static PWs. This document also updates RFC 5885 in the case when Bi-directional Forwarding Detection (BFD) is used to convey PW status-signaling information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6478
- Published
- May 2012
- Authors
- L. Martini; G. Swallow; G. Heron; M. Bocci
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6480An Infrastructure to Support Secure Internet RoutingCurrent
February 2012
- RFC 6481A Profile for Resource Certificate Repository StructureCurrent
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6472Recommendation for Not Using AS_SET and AS_CONFED_SET in BGPObsoleted
December 2011
- RFC 6484Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)Current
February 2012
- RFC 6485The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
- RFC 6486Manifests for the Resource Public Key Infrastructure (RPKI)Obsoleted
February 2012
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?