RFC 8237: MPLS Label Switched Path (LSP) Pseudowire (PW) Status Refresh Reduction for Static PWs
In plain English — editorial summary, not part of the RFC
This document describes a method for generating an aggregated pseudowire (PW) status message transmitted for a statically configured PW on a Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) to indicate the status of one or more PWs carried on the LSP. The method for transmitting the PW status information is not new; however, this protocol extension allows a Service Provider (SP) to reliably monitor the individual PW status while not overwhelming the network with multiple periodic status messages. This is achieved by sending a single cumulative summary status verification message for all the PWs grouped in the same LSP.
Document record
- Document ID
- RFC8237
- Published
- October 2017
- Authors
- L. Martini; G. Swallow; E. Bellagamba
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8234Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) ModeCurrent
August 2017
- RFC 8233Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)Updated
September 2017
- RFC 8241Interface to the Routing System (I2RS) Security-Related RequirementsCurrent
September 2017
- RFC 8232Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCECurrent
September 2017
- RFC 8242Interface to the Routing System (I2RS) Ephemeral State RequirementsCurrent
September 2017
- RFC 8231Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCEUpdated
September 2017
- RFC 8243Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)Current
September 2017
- RFC 8245Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444Current
October 2017
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?