I-D Action:draft-ietf-tsvwg-rsvp-proxy-proto-10.txt

Internet-Drafts@ietf.org Mon, 26 October 2009 11:15 UTC

Return-Path: <root@core3.amsl.com>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 6875E28C0D0; Mon, 26 Oct 2009 04:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-tsvwg-rsvp-proxy-proto-10.txt
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20091026111501.6875E28C0D0@core3.amsl.com>
Date: Mon, 26 Oct 2009 04:15:01 -0700
Cc: tsvwg@ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 11:15: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 Extensions for Path-Triggered RSVP Receiver Proxy
	Author(s)       : F. Le Faucheur, et al.
	Filename        : draft-ietf-tsvwg-rsvp-proxy-proto-10.txt
	Pages           : 40
	Date            : 2009-10-26

RSVP signaling can be used to make end-to-end resource reservations
in an IP network in order to guarantee the QoS required by certain
flows.  With conventional RSVP, 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.  Where the receiver is not
RSVP-capable, an RSVP router may behave as an RSVP Receiver Proxy
thereby performing RSVP signaling on behalf of the receiver.  This
allows resource reservations to be established on the segment of the
end-to-end path from the sender to the RSVP Receiver Proxy.  However,
as discussed in the companion document presenting RSVP Proxy
approaches, RSVP extensions are needed to facilitate operations with
an RSVP Receiver Proxy whose signaling is triggered by receipt of
RSVP Path messages from the sender.  This document specifies these
extensions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-proto-10.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-proto-10.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-proto-10.txt>