Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 38
- Abstract
- In a distributed, constraint-based routing environment, the information used to compute a path may be out of date. This means that Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) Label Switched Path (LSP) setup requests may be blocked by links or nodes without sufficient resources. Crankback is a scheme whereby setup failure information is returned from the point of failure to allow new setup attempts to be made avoiding the blocked resources. Crankback can also be applied to LSP recovery to indicate the location of the failed link or node. This document specifies crankback signaling extensions for use in MPLS signaling using RSVP-TE as defined in "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, and GMPLS signaling as defined in "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3473. These extensions mean that the LSP setup request can be retried on an alternate path that detours around blocked links or nodes. This offers significant improvements in the successful setup and recovery ratios for LSPs, especially in situations where a large number of setup requests are triggered at the same time. [STANDARDS-TRACK]
- Publication Date
- 2007-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4920- Link
- https://doi.org/10.17487/RFC4920
- Author(s)
- Adrian FarrelArun SatyanarayanaAtsushi IwataNorihito FujitaGerald Ash
- Keyword(s)
- MPLS, GMPLS, MPLS-TE, TE LSP, LSP
Latest version of IETF RFC 4920
Document Versions — IETF RFC 4920
-
▶ IETF RFC 4920 (2007-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2205 [Active*]
- IETF RFC 3209 [Active*]
- IETF RFC 3471 [Active*]
- IETF RFC 3473 [Active*]
- IETF RFC 4420 [Superseded*]
Bibliographic Reference(s)
- ATM Forum, "Private Network-Network Interface Specification Version 1.0 (PNNI 1.0)", <af-pnni-0055.000>, May 1996. EXTERNAL
- IETF RFC 2702 [Active*]
- IETF RFC 3469 [Active*]
- IETF RFC 4090 [Active*]
- IETF RFC 4201 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 4874 [Active*]
- T-REC-E.360.2002 — ASH1 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4920.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4920, Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE. Available at https://doi.org/10.17487/RFC4920
Snippet:
IETF RFC 4920, Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE. Available at https://doi.org/10.17487/RFC4920
HTML (ISO 690 compliant)
Preview:
IETF RFC 4920, Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE. Available at https://doi.org/10.17487/RFC4920
Snippet:
<span class="citation"><cite>IETF RFC 4920</cite>, Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE. Available at <a href="https://doi.org/10.17487/RFC4920" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4920</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4920, Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
doi: 10.17487/RFC4920
url: https://doi.org/10.17487/RFC4920
doi: 10.17487/RFC4920
url: https://doi.org/10.17487/RFC4920
Snippet:
<li> <cite id="bib-rfc4920">IETF RFC 4920</cite>, Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE <span class="doi">10.17487/RFC4920</span> </li>
Referenced By
- IETF RFC 5151 [Active*]
- IETF RFC 5152 [Active*]
- IETF RFC 5298 [Active*]
- IETF RFC 5623 [Active*]
- IETF RFC 5710 [Active*]
- IETF RFC 6601 [Active*]
- IETF RFC 8390 [Active*]