I-D ACTION:draft-ietf-l3vpn-e2e-rsvp-te-reqts-02.txt

Internet-Drafts@ietf.org Mon, 03 November 2008 18:15 UTC

Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32C5428C124; Mon, 3 Nov 2008 10:15:03 -0800 (PST)
X-Original-To: l3vpn@ietf.org
Delivered-To: l3vpn@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4A1D93A6B6B; Mon, 3 Nov 2008 10:15:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-e2e-rsvp-te-reqts-02.txt
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081103181501.4A1D93A6B6B@core3.amsl.com>
Date: Mon, 03 Nov 2008 10:15:01 -0800
Cc: l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN
	Author(s)	: K. Kumaki, Y. Kamite, R. Zhang
	Filename	: draft-ietf-l3vpn-e2e-rsvp-te-reqts-02.txt
	Pages		: 22
	Date		: 2008-11-3
	
Some service providers want to build a service which guarantees QoS 
   or bandwidth from a local CE to a remote CE through the network. 
   Today, customers expect to run triple play services through BGP/MPLS 
   IP-VPNs. As a result, their requirements for end-to-end QoS of 
   applications are increasing. Depending on the application (e.g., 
   voice, video, bandwidth-guaranteed data pipe, etc.), an end-to-end 
   native RSVP path and/or an end-to-end MPLS TE LSP are required, and 
   they need to meet some constraints. 
   This document describes service provider requirements for supporting 
   customer RSVP and RSVP-TE over a BGP/MPLS VPN.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-e2e-rsvp-te-reqts-02.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-l3vpn-e2e-rsvp-te-reqts-02.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-l3vpn-e2e-rsvp-te-reqts-02.txt>