[Tsvwg] RFC 4495 on A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation Flow

rfc-editor@rfc-editor.org Sat, 06 May 2006 00:42 UTC

Date: Fri, 05 May 2006 17:42:05 -0700
Message-Id: <200605060042.k460g59k032526@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Tsvwg] RFC 4495 on A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation Flow
Precedence: list
Errors-To: tsvwg-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4495

        Title:      A Resource Reservation Protocol (RSVP) 
                    Extension for the Reduction of Bandwidth 
                    of a Reservation Flow 
        Author:     J. Polk, S. Dhesikan
        Status:     Standards Track
        Date:       May 2006
        Mailbox:    jmpolk@cisco.com, 
                    sdhesika@cisco.com
        Pages:      21
        Characters: 44983
        Updates:    RFC2205
        See-Also:   

        I-D Tag:    draft-ietf-tsvwg-rsvp-bw-reduction-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4495.txt

This document proposes an extension to the Resource Reservation
Protocol (RSVPv1) to reduce the guaranteed bandwidth allocated to an
existing reservation.  This mechanism can be used to affect
individual reservations, aggregate reservations, or other forms of
RSVP tunnels.  This specification is an extension of RFC 2205.  
[STANDARDS TRACK]

This document is a product of the Transport Area Working Group
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

[Tsvwg] RFC 4495 on A Resource Reservation Protoc… rfc-editor