Fwd: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-l3vpn-00.txt

[Bruce Davie <[e-mail]>]

This draft has been presented to L3VPN a couple of times, but is now  
getting progressed in TSVWG as discussed at the last IETF. If you  
want to comment on it, please copy the tsvwg list.

Bruce

Begin forwarded message:

> From: [e-mail]
> Date: July 3, 2008 1:30:01 PM EDT
> To: [e-mail]
> Cc: [e-mail]
> Subject: [Tsvwg] I-D Action:draft-ietf-tsvwg-rsvp-l3vpn-00.txt
>
> 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           : Support for RSVP in Layer 3 VPNs
> 	Author(s)       : B. Davie, et al.
> 	Filename        : draft-ietf-tsvwg-rsvp-l3vpn-00.txt
> 	Pages           : 32
> 	Date            : 2008-07-03
>
> RFC 4364 and RFC 4659 define an approach to building provider-
> provisioned Layer 3 VPNs for IPv4 and IPv6.  It may be desirable to
> use RSVP to perform admission control on the links between CE and PE
> routers.  This document specifies procedures by which RSVP messages
> travelling 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.Requirements Language
>
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in RFC 2119 [RFC2119].
>
> Change history
>
> [_Note to RFC Editor: This section to be removed before publication_]
>
> Changes in this version (draft-ietf-tsvwg-rsvp-l3vpn-00) relative to
> the last (draft-davie-tsvwg-rsvp-l3vpn-02):
>
> o  Outlined signalling security issues and added discussion of
>
> methods to control redistribution of routes among providers and
>
> from providers to customers
>
> o  Clarification regarding support for RSVP-TE across L3VPN
>
> o  Minor corrections
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-l3vpn-00.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.
> Content-Type: text/plain
> Content-ID: <[e-mail]>
>