RFC 7260

GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) Configuration, June 2014

File formats:
icon for text file icon for PDF icon for HTML icon for inline errata
A. Takacs
D. Fedyk
J. He
ccamp (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7260

Discuss this RFC: Send questions or comments to the mailing list ccamp@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7260


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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search