Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5852
Discuss this RFC: Send questions or comments to the mailing listccamp@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5852
In a transport network scenario, Data Plane connections controlled byeither a Generalized Multiprotocol Label Switching (GMPLS) ControlPlane (Soft Permanent Connections - SPC) or a Management System(Permanent Connections - PC) may independently coexist. The abilityof transforming an existing PC into an SPC and vice versa -- withoutactually affecting Data Plane traffic being carried over it -- is arequirement. The requirements for the conversion between permanentconnections and switched connections in a GMPLS Network are definedin RFC 5493.
This memo describes an extension to GMPLS Resource ReservationProtocol - Traffic Engineering (RSVP-TE) signaling that enables thetransfer of connection ownership between the Management and theControl Planes. Such a transfer is referred to as a Handover. Thisdocument defines all Handover-related procedures. This includes thehandling of failure conditions and subsequent reversion to originalstate. A basic premise of the extension is that the Handoverprocedures must never impact an already established Data Planeconnection. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.