RFC 8256
Requirements for Hitless MPLS Path Segment Monitoring, October 2017
- File formats:
- Status:
- INFORMATIONAL
- Authors:
- A. D'Alessandro
L. Andersson
S. Ueno
K. Arai
Y. Koike - Stream:
- IETF
- Source:
- mpls (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8256
Discuss this RFC: Send questions or comments to the mailing list mpls@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8256
Abstract
One of the most important Operations, Administration, and Maintenance (OAM) capabilities for transport-network operation is fault localization. An in-service, on-demand path segment monitoring function of a transport path is indispensable, particularly when the service monitoring function is activated only between endpoints. However, the current segment monitoring approach defined for MPLS (including the MPLS Transport Profile (MPLS-TP)) in RFC 6371 "Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks" has drawbacks. This document provides an analysis of the existing MPLS-TP OAM mechanisms for the path segment monitoring and provides requirements to guide the development of new OAM tools to support Hitless Path Segment Monitoring (HPSM).
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.