Pseudowire Status for Static Pseudowires, May 2012
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- RFC 5885
- Updated by:
- RFC 7274
- L. Martini
- pwe3 (rtg)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.