[Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt

Internet-Drafts@ietf.org Thu, 14 May 2009 12:00 UTC

Return-Path: <root@core3.amsl.com>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9699B28B56A; Thu, 14 May 2009 05:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090514120001.9699B28B56A@core3.amsl.com>
Date: Thu, 14 May 2009 05:00:01 -0700
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2009 12:00:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.


	Title           : RSVP Proxy Approaches
	Author(s)       : F. Le Faucheur, et al.
	Filename        : draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt
	Pages           : 48
	Date            : 2009-05-14

The Resource ReSerVation Protocol (RSVP) can be used to make end-to-
end resource reservations in an IP network in order to guarantee the
quality of service required by certain flows.  RSVP assumes that both
the data sender and receiver of a given flow take part in RSVP
signaling.  Yet, there are many use cases where resource reservation
is required, but the receiver, the sender, or both, is not RSVP-
capable.  This document presents RSVP Proxy behaviors allowing RSVP
routers to initiate or terminate RSVP signaling on behalf of a
receiver or a sender that is not RSVP-capable.  This allows resource
reservations to be established on a critical subset of the end-to-end
path.  This document reviews conceptual approaches for deploying RSVP
Proxies and discusses how RSVP reservations can be synchronized with
application requirements, despite the sender, receiver, or both not
participating in RSVP.  This document also points out where
extensions to RSVP (or to other protocols) may be needed for
deployment of a given RSVP Proxy approach.  However, such extensions
are outside the scope of this document.  Finally, practical use cases
for RSVP Proxy are described.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt>