Requirements for Hitless MPLS Path Segment Monitoring
RFC 8256, “Requirements for Hitless MPLS Path Segment Monitoring”, is an Informational document published in October 2017 by A. D'Alessandro, L. Andersson, S. Ueno, K. Arai, Y. Koike. The canonical text is published by the RFC Editor.
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).
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8256 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8255 Multiple Language Content Type
- RFC 8257 Data Center TCP : TCP Congestion Control for Data Centers
- RFC 8254 Uniform Resource Name Namespace Registration Transition
- RFC 8258 Generalized SCSI: A Generic Structure for Interface Switching Capability Descriptor Switching Capability Specific Information
- RFC 8253 PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol
- RFC 8259 The JavaScript Object Notation Data Interchange Format
- RFC 8252 OAuth 2.0 for Native Apps
- RFC 8260 Stream Schedulers and User Message Interleaving for the Stream Control Transmission Protocol