GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance Configuration
RFC 7260, “GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance Configuration”, is a Proposed Standard document published in June 2014 by A. Takacs, D. Fedyk, J. He. The canonical text is published by the RFC Editor.
Abstract
Operations, Administration, and Maintenance (OAM) is an integral part of transport connections; hence, it is required that OAM functions be activated/deactivated in sync with connection commissioning/ decommissioning, in order to avoid spurious alarms and ensure consistent operation. In certain technologies, OAM entities are inherently established once the connection is set up, while other technologies require extra configuration to establish and configure OAM entities. This document specifies extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) to support the establishment and configuration of OAM entities along with Label Switched Path signaling.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7260 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7259 The Jabber-ID Header Field
- RFC 7261 Offer/Answer Considerations for G723 Annex A and G729 Annex B
- RFC 7258 Pervasive Monitoring Is an Attack
- RFC 7262 Requirements for Telepresence Multistreams
- RFC 7257 Virtual Private LAN Service Management Information Base
- RFC 7263 An Extension to the REsource LOcation And Discovery Protocol to Support Direct Response Routing
- RFC 7256 Multicast Control Extensions for the Access Node Control Protocol
- RFC 7264 An Extension to the REsource LOcation And Discovery Protocol to Support Relay Peer Routing