Browse Prior Art Database

RSVP Refresh Overhead Reduction Extensions (RFC2961)

IP.com Disclosure Number: IPCOM000005154D
Original Publication Date: 2001-Apr-01
Included in the Prior Art Database: 2001-Aug-16
Document File: 35 page(s) / 82K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Berger: AUTHOR [+6]

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.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 5% of the total text.

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...