RFC 5063: Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart
In plain English — editorial summary, not part of the RFC
This document describes extensions to the Resource Reservation Protocol (RSVP) Graceful Restart mechanisms defined in RFC 3473. The extensions enable the recovery of RSVP signaling state based on the Path message last sent by the node being restarted. Previously defined Graceful Restart mechanisms, also called recovery from nodal faults, permit recovery of signaling state from adjacent nodes when the data plane has retained the associated forwarding state across a restart. Those mechanisms do not fully support signaling state recovery on ingress nodes or recovery of all RSVP objects. The extensions defined in this document build on the RSVP Hello extensions defined in RFC 3209, and extensions for state recovery on nodal faults defined in RFC 3473. Using these extensions, the restarting node can recover all previously transmitted Path state, including the Explicit Route Object and the downstream (outgoing) interface identifiers. The extensions can also be used to recover signaling state after the restart of an ingress node. These extensions are not used to create or restore data plane state. The extensions optionally support the use of Summary Refresh, defined in RFC 2961, to reduce the number of messages exchanged during the Recovery Phase when the restarting node has recovered signaling state locally for one or more Label Switched Paths (LSPs). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5063
- Published
- October 2007
- Authors
- A. Satyanarayana; R. Rahman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
- RFC 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 5059Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)Updated
January 2008
- RFC 5073IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node CapabilitiesCurrent
December 2007
- RFC 5082The Generalized TTL Security Mechanism (GTSM)Current
October 2007
- RFC 5085Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for PseudowiresUpdated
December 2007
- RFC 5086Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)Current
December 2007
- RFC 5087Time Division Multiplexing over IP (TDMoIP)Current
December 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?