RFC 6016 on Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs
rfc-editor@rfc-editor.org Wed, 06 October 2010 19:16 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93B5C3A70B8; Wed, 6 Oct 2010 12:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level:
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=-0.584, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m3WlrBqMZ5XO; Wed, 6 Oct 2010 12:16:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 34E153A71C0; Wed, 6 Oct 2010 12:16:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 32CFDE0725; Wed, 6 Oct 2010 12:17:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6016 on Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs
From: rfc-editor@rfc-editor.org
Message-Id: <20101006191727.32CFDE0725@rfc-editor.org>
Date: Wed, 06 Oct 2010 12:17:27 -0700
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
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: Wed, 06 Oct 2010 19:16:30 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6016 Title: Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs Author: B. Davie, F. Le Faucheur, A. Narayanan Status: Standards Track Stream: IETF Date: October 2010 Mailbox: bsd@cisco.com, flefauch@cisco.com, ashokn@cisco.com Pages: 38 Characters: 95185 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-tsvwg-rsvp-l3vpn-07.txt URL: http://www.rfc-editor.org/rfc/rfc6016.txt RFC 4364 and RFC 4659 define an approach to building provider-provisioned Layer 3 VPNs (L3VPNs) for IPv4 and IPv6. It may be desirable to use Resource Reservation Protocol (RSVP) to perform admission control on the links between Customer Edge (CE) routers and Provider Edge (PE) routers. This document specifies procedures by which RSVP messages traveling from CE to CE across an L3VPN may be appropriately handled by PE routers so that admission control can be performed on PE-CE links. Optionally, admission control across the provider's backbone may also be supported. [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-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC