Skip to main content

Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart Procedures
RFC 5495

Revision differences

Document history

Date Rev. By Action
2018-12-20
04 (System)
Received changes through RFC Editor sync (changed abstract to 'The Hello message for the Resource Reservation Protocol (RSVP) has been defined to establish and maintain …
Received changes through RFC Editor sync (changed abstract to 'The Hello message for the Resource Reservation Protocol (RSVP) has been defined to establish and maintain basic signaling node adjacencies for Label Switching Routers (LSRs) participating in a Multiprotocol Label Switching (MPLS) traffic-engineered (TE) network. The Hello message has been extended for use in Generalized MPLS (GMPLS) networks for state recovery of control channel or nodal faults.

The GMPLS protocol definitions for RSVP also allow a restarting node to learn which label it previously allocated for use on a Label Switched Path (LSP).

Further RSVP protocol extensions have been defined to enable a restarting node to recover full control plane state by exchanging RSVP messages with its upstream and downstream neighbors.

This document provides an informational clarification of the control plane procedures for a GMPLS network when there are multiple node failures, and describes how full control plane state can be recovered in different scenarios where the order in which the nodes restart is different.

This document does not define any new processes or procedures. All protocol mechanisms are already defined in the referenced documents. This memo provides information for the Internet community.')
2015-10-14
04 (System) Notify list changed from ccamp-chairs@ietf.org, draft-ietf-ccamp-gr-description@ietf.org to (None)
2010-08-19
(System) Posted related IPR disclosure: Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 5495
2010-08-05
(System) Posted related IPR disclosure: Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 5495
2009-03-16
04 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2009-03-16
04 Amy Vezza [Note]: 'RFC 5495' added by Amy Vezza
2009-03-13
04 (System) RFC published
2009-02-17
04 Cindy Morgan State Changes to RFC Ed Queue from Approved-announcement sent by Cindy Morgan
2009-02-17
04 (System) IANA Action state changed to No IC from In Progress
2009-02-17
04 (System) IANA Action state changed to In Progress
2009-02-17
04 Amy Vezza IESG state changed to Approved-announcement sent
2009-02-17
04 Amy Vezza IESG has approved the document
2009-02-17
04 Amy Vezza Closed "Approve" ballot
2009-02-13
04 Amy Vezza State Changes to Approved-announcement to be sent from IESG Evaluation by Amy Vezza
2009-02-13
04 (System) Removed from agenda for telechat - 2009-02-12
2009-02-12
04 David Ward [Ballot Position Update] New position, Yes, has been recorded by David Ward
2009-02-12
04 Tim Polk
[Ballot comment]
I know this is a nit, but there are extraneous commas in the two most important sentences
in this specification.  To remove ambiguity, …
[Ballot comment]
I know this is a nit, but there are extraneous commas in the two most important sentences
in this specification.  To remove ambiguity, I would suggest the following substitution in
Section 6:

OLD
  After a node restarts its control plane, it should ignore and
  silently drop all RSVP-TE messages, except Hello messages, it
  receives from any neighbor to which, no HELLO session has been
  established.
NEW
  After a node restarts its control plane, it should ignore and
  silently drop all RSVP-TE messages, except Hello messages, it
  receives from any neighbor to which no HELLO session has been
  established.

OLD
  The restarting node should follow [RFC3209] to establish Hello
  sessions with its neighbors, after its control plane becomes
  operational.
NEW
  The restarting node should follow [RFC3209] to establish Hello
  sessions with its neighbors after its control plane becomes
  operational.
2009-02-12
04 Tim Polk [Ballot Position Update] New position, No Objection, has been recorded by Tim Polk
2009-02-12
04 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded by Jari Arkko
2009-02-12
04 Chris Newman [Ballot Position Update] New position, No Objection, has been recorded by Chris Newman
2009-02-11
04 Russ Housley [Ballot Position Update] New position, No Objection, has been recorded by Russ Housley
2009-02-11
04 Mark Townsley [Ballot Position Update] New position, No Objection, has been recorded by Mark Townsley
2009-02-11
04 Pasi Eronen [Ballot Position Update] New position, No Objection, has been recorded by Pasi Eronen
2009-02-10
04 Lars Eggert [Ballot Position Update] New position, No Objection, has been recorded by Lars Eggert
2009-02-06
04 Samuel Weiler Request for Last Call review by SECDIR Completed. Reviewer: Love Astrand.
2009-01-27
04 Ross Callon Placed on agenda for telechat - 2009-02-12 by Ross Callon
2009-01-27
04 Ross Callon State Changes to IESG Evaluation from Waiting for AD Go-Ahead by Ross Callon
2009-01-27
04 Ross Callon [Ballot Position Update] New position, Yes, has been recorded for Ross Callon
2009-01-27
04 Ross Callon Ballot has been issued by Ross Callon
2009-01-27
04 Ross Callon Created "Approve" ballot
2009-01-20
04 (System) New version available: draft-ietf-ccamp-gr-description-04.txt
2009-01-20
04 (System) State has been changed to Waiting for AD Go-Ahead from In Last Call by system
2009-01-15
04 Samuel Weiler Request for Last Call review by SECDIR is assigned to Love Astrand
2009-01-15
04 Samuel Weiler Request for Last Call review by SECDIR is assigned to Love Astrand
2009-01-15
04 Amanda Baber IANA Last Call comments:

As described in the IANA Considerations section, we understand
this document to have NO IANA Actions.
2009-01-06
04 Amy Vezza Last call sent
2009-01-06
04 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2009-01-06
04 Ross Callon State Changes to Last Call Requested from Publication Requested by Ross Callon
2009-01-06
04 Ross Callon Last Call was requested by Ross Callon
2009-01-06
04 (System) Ballot writeup text was added
2009-01-06
04 (System) Last call text was added
2009-01-06
04 (System) Ballot approval text was added
2008-10-31
04 Ross Callon
PROTO writeup by Deborah Brungard:

Intended status : Informational

> (1.a)  Who is the Document Shepherd for this document?  Has the
>        …
PROTO writeup by Deborah Brungard:

Intended status : Informational

> (1.a)  Who is the Document Shepherd for this document?  Has the
>        Document Shepherd personally reviewed this version of the
>        document and, in particular, does he or she believe this
>        version is ready for forwarding to the IESG for publication?

Deborah Brungard is the document shepherd.
She has personally reviewed the I-D and believes it is ready for
forwarding to the IESG for publication.

> (1.b)  Has the document had adequate review both from key WG members
>        and from key non-WG members?  Does the Document Shepherd have
>        any concerns about the depth or breadth of the reviews that
>        have been performed?

This document has been reviewed by the CCAMP working group and received
some comments at IETF meetings and on the mailing list. Most importantly
it has had input from the authors of RFC 5063 that documents the
protocol procedures.

> (1.c)  Does the Document Shepherd have concerns that the document
>        needs more review from a particular or broader perspective,
>        e.g., security, operational complexity, someone familiar with
>        AAA, internationalization or XML?

No concerns.

> (1.d)  Does the Document Shepherd have any specific concerns or
>        issues with this document that the Responsible Area Director
>        and/or the IESG should be aware of?  For example, perhaps he
>        or she is uncomfortable with certain parts of the document, or
>        has concerns whether there really is a need for it.  In any
>        event, if the WG has discussed those issues and has indicated
>        that it still wishes to advance the document, detail those
>        concerns here.  Has an IPR disclosure related to this document
>        been filed?  If so, please include a reference to the
>        disclosure and summarize the WG discussion and conclusion on
>        this issue.

The document is sound.
No IPR disclosures filed.

> (1.e)  How solid is the WG consensus behind this document?  Does it
>        represent the strong concurrence of a few individuals, with
>        others being silent, or does the WG as a whole understand and
>        agree with it?

There were no problems with consensus for this document.


> (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
>        discontent?  If so, please summarise the areas of conflict in
>        separate email messages to the Responsible Area Director.  (It
>        should be in a separate email because this questionnaire is
>        entered into the ID Tracker.)

No threats. No discontent.

> (1.g)  Has the Document Shepherd personally verified that the
>        document satisfies all ID nits?  (See
>        http://www.ietf.org/ID-Checklist.html and
>        http://tools.ietf.org/tools/idnits/).  Boilerplate checks are
>        not enough; this check needs to be thorough.  Has the document
>        met all formal review criteria it needs to, such as the MIB
>        Doctor, media type and URI type reviews?

All checks made.

> (1.h)  Has the document split its references into normative and
>        informative?  Are there normative references to documents that
>        are not ready for advancement or are otherwise in an unclear
>        state?  If such normative references exist, what is the
>        strategy for their completion?  Are there normative references
>        that are downward references, as described in [RFC3967]?  If
>        so, list these downward references to support the Area
>        Director in the Last Call procedure for them [RFC3967].

References split.
No downrefs.

> (1.i)  Has the Document Shepherd verified that the document IANA
>        consideration section exists and is consistent with the body
>        of the document?  If the document specifies protocol
>        extensions, are reservations requested in appropriate IANA
>        registries?  Are the IANA registries clearly identified?  If
>        the document creates a new registry, does it define the
>        proposed initial contents of the registry and an allocation
>        procedure for future registrations?  Does it suggest a
>        reasonable name for the new registry?  See [RFC2434].  If the
>        document describes an Expert Review process has Shepherd
>        conferred with the Responsible Area Director so that the IESG
>        can appoint the needed Expert during the IESG Evaluation?

This is an Informational I-D that makes no requestes of IANA.
A Null IANA section is included.

> (1.j)  Has the Document Shepherd verified that sections of the
>        document that are written in a formal language, such as XML
>        code, BNF rules, MIB definitions, etc., validate correctly in
>        an automated checker?

No formal language used.

> (1.k)  The IESG approval announcement includes a Document
>        Announcement Write-Up.  Please provide such a Document
>        Announcement Write-Up.  Recent examples can be found in the
>        "Action" announcements for approved documents.  The approval
>        announcement contains the following sections:
>
>        Technical Summary
>          Relevant content can frequently be found in the abstract
>          and/or introduction of the document.  If not, this may be
>          an indication that there are deficiencies in the abstract
>          or introduction.

The Hello message for the Resource Reservation Protocol (RSVP) has
been defined to establish and maintain basic signaling node
adjacencies for Label Switching Routers (LSRs) participating in a
Multiprotocol Label Switching (MPLS) traffic engineered (TE)
network. The Hello message has been extended for use in Generalized
MPLS (GMPLS) network for state recovery of control channel or nodal
faults.

GMPLS protocol definitions for RSVP also allow a restarting node to
learn the label that it previously allocated for use on a Label
Switching Path (LSP).

Further RSVP protocol extensions have been defined to enable a
restarting node to recover full control plane state by exchanging
RSVP messages with its upstream and downstream neighbors.

This document provides an informational clarification of the
control plane procedures for a GMPLS network when there are
multiple node failures, and describes how full control plane state
can be recovered in different scenarios where the order in which
the nodes restart is different.

This document does not define any new processes or procedures. All
protocol mechanisms are already defined in the referenced documents.

>        Working Group Summary
>          Was there anything in WG process that is worth noting?  For
>          example, was there controversy about particular points or
>          were there decisions where the consensus was particularly
>          rough?

There was some debate about the need for this work. It was suggested
that all of the necessary explanation of the operation of graceful
restart was included in RFC 5063. However, the repeated questions about
how to use the protocol extensions in corner cases and double faliure
scenarios makes this work valuable.

Otherwise, all parts of the WG process were normal.

>        Document Quality
>          Are there existing implementations of the protocol?  Have a
>          significant number of vendors indicated their plan to
>          implement the specification?  Are there any reviewers that
>          merit special mention as having done a thorough review,
>          e.g., one that resulted in important changes or a
>          conclusion that the document had no substantive issues?  If
>          there was a MIB Doctor, Media Type or other expert review,
>          what was its course (briefly)?  In the case of a Media Type
>          review, on what date was the request posted?

There are several implementations of the graceful restart processes
described in RFC 5063. Experience from these implementations has
provided valuable input to this document.
2008-10-31
04 Ross Callon Draft Added by Ross Callon in state Publication Requested
2008-05-19
03 (System) New version available: draft-ietf-ccamp-gr-description-03.txt
2008-05-05
02 (System) New version available: draft-ietf-ccamp-gr-description-02.txt
2007-11-16
01 (System) New version available: draft-ietf-ccamp-gr-description-01.txt
2007-08-14
00 (System) New version available: draft-ietf-ccamp-gr-description-00.txt