idnits 2.17.1 draft-ietf-rsvp-refresh-reduct-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 2961 5 Title: RSVP Refresh Overhead Reduction Extensions 6 Author(s): L. Berger, D. Gan, G. Swallow, P. Pan, F. Tommasi, 7 S. Molendini 8 Status: Standards Track 9 Date: April 2001 10 Mailbox: lberger@labn.net, dhg@juniper.net, 11 swallow@cisco.com, pingpan@juniper.net, 12 franco.tommasi@unile.it, molendini@ultra5.unile.it 13 Pages: 34 14 Characters: 81675 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-rsvp-refresh-reduct-05.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc2961.txt 21 This document describes a number of mechanisms that can be used to 22 reduce processing overhead requirements of refresh messages, eliminate 23 the state synchronization latency incurred when an RSVP (Resource 24 ReserVation Protocol) message is lost and, when desired, refreshing 25 state without the transmission of whole refresh messages. The same 26 extensions also support reliable RSVP message delivery on a per hop 27 basis. These extension present no backwards compatibility issues. 29 This document is a prodcut of the Resource Reservation Setup Protocol 30 Working Group of the IETF. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.