RFC 4974: Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls
In plain English — editorial summary, not part of the RFC
In certain networking topologies, it may be advantageous to maintain associations between endpoints and key transit points to support an instance of a service. Such associations are known as Calls. A Call does not provide the actual connectivity for transmitting user traffic, but only builds a relationship by which subsequent Connections may be made. In Generalized MPLS (GMPLS) such Connections are known as Label Switched Paths (LSPs). This document specifies how GMPLS Resource Reservation Protocol - Traffic Engineering (RSVP-TE) signaling may be used and extended to support Calls. These mechanisms provide full and logical Call/Connection separation. The mechanisms proposed in this document are applicable to any environment (including multi-area), and for any type of interface: packet, layer-2, time-division multiplexed, lambda, or fiber switching. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4974
- Published
- August 2007
- Authors
- D. Papadimitriou; A. Farrel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 31
- Also known as
- —
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 4971Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router InformationObsoleted
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 4990Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) NetworksCurrent
September 2007
- RFC 4951Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"Current
August 2007
- RFC 4950ICMP Extensions for Multiprotocol Label SwitchingCurrent
August 2007
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
- RFC 5004Avoid BGP Best Path Transitions from One External to AnotherCurrent
September 2007
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?