RSVP Refresh Overhead Reduction Extensions
RFC 2961

Document Type RFC - Proposed Standard (April 2001; No errata)
Updated by RFC 5063
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2961 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         L. Berger
Request for Comments: 2961                         LabN Consulting, LLC
Category: Standards Track                                        D. Gan
                                                 Juniper Networks, Inc.
                                                             G. Swallow
                                                    Cisco Systems, Inc.
                                                                 P. Pan
                                                 Juniper Networks, Inc.
                                                             F. Tommasi
                                                           S. Molendini
                                                    University of Lecce
                                                             April 2001

               RSVP Refresh Overhead Reduction Extensions

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

Abstract

   This document describes a number of mechanisms that can be used to
   reduce processing overhead requirements of refresh messages,
   eliminate the state synchronization latency incurred when an RSVP
   (Resource ReserVation Protocol) message is lost and, when desired,
   refreshing state without the transmission of whole refresh messages.
   The same extensions also support reliable RSVP message delivery on a
   per hop basis.  These extension present no backwards compatibility
   issues.

Berger, et al.              Standards Track                     [Page 1]
RFC 2961       RSVP Refresh Overhead Reduction Extensions     April 2001

Table of Contents

   1      Introduction and Background ................................2
   1.1    Trigger and Refresh Messages ...............................4
   2      Refresh-Reduction-Capable Bit ..............................4
   3      RSVP Bundle Message ........................................5
   3.1    Bundle Header ..............................................5
   3.2    Message Formats ............................................6
   3.3    Sending RSVP Bundle Messages ...............................7
   3.4    Receiving RSVP Bundle Messages .............................8
   4      MESSAGE_ID Extension .......................................8
   4.1    Modification of Standard Message Formats ...................9
   4.2    MESSAGE_ID Objects ........................................10
   4.3    MESSAGE_ID_ACK and MESSAGE_ID_NACK Objects ................11
   4.4    Ack Message Format ........................................11
   4.5    MESSAGE_ID Object Usage ...................................12
   4.6    MESSAGE_ID_ACK Object and MESSAGE_ID_NACK Object Usage ....14
   4.7    Multicast Considerations ..................................15
   4.7.1  Reference RSVP/Routing Interface ..........................16
   4.8    Compatibility .............................................16
   5      Summary Refresh Extension .................................17
   5.1    MESSAGE_ID LIST, SRC_LIST and MCAST_LIST Objects ..........18
   5.2    Srefresh Message Format ...................................24
   5.3    Srefresh Message Usage ....................................25
   5.4    Srefresh NACK .............................................28
   5.5    Preserving RSVP Soft State ................................28
   5.6    Compatibility .............................................29
   6      Exponential Back-Off Procedures ...........................29
   6.1    Outline of Operation ......................................30
   6.2    Time Parameters ...........................................30
   6.3    Retransmission Algorithm ..................................31
   6.4    Performance Considerations ................................31
   7      Acknowledgments ...........................................31
   8      Security Considerations ...................................32
   9      References ................................................32
   10     Authors' Addresses ........................................33
   11     Full Copyright Statement...................................34

1. Introduction and Background

   Standard RSVP [RFC2205] maintains state via the generation of RSVP
   refresh messages.  Refresh messages are used to both synchronize
   state between RSVP neighbors and to recover from lost RSVP messages.
   The use of Refresh messages to cover many possible failures has
   resulted in a number of operational problems.  One problem relates to
   scaling, another relates to the reliability and latency of RSVP
Show full document text