RFC 5493: Requirements for the Conversion between Permanent Connections and Switched Connections in a Generalized Multiprotocol Label Switching (GMPLS) Network
In plain English — editorial summary, not part of the RFC
From a carrier perspective, the possibility of turning a permanent connection (PC) into a soft permanent connection (SPC) and vice versa, without actually affecting data plane traffic being carried over it, is a valuable option. In other terms, such operation can be seen as a way of transferring the ownership and control of an existing and in-use data plane connection between the management plane and the control plane, leaving its data plane state untouched. This memo sets out the requirements for such procedures within a Generalized Multiprotocol Label Switching (GMPLS) network. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5493
- Published
- April 2009
- Authors
- D. Caviglia; D. Bramanti; D. Li; D. McDysan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4504SIP Telephony Device Requirements and ConfigurationCurrent
May 2006
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 5495Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart ProceduresCurrent
March 2009
- RFC 5496The Reverse Path Forwarding (RPF) Vector TLVCurrent
March 2009
- RFC 5497Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)Current
March 2009
- RFC 5498IANA Allocations for Mobile Ad Hoc Network (MANET) ProtocolsCurrent
March 2009
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 5467GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)Obsoleted
March 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?