Support for RSVP in Layer 3 VPNs
draft-davie-tsvwg-rsvp-l3vpn-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Dr. Bruce S. Davie , François Le Faucheur , Ashok Narayanan | ||
Last updated | 2008-07-07 (Latest revision 2008-02-25) | ||
Replaced by | draft-ietf-tsvwg-rsvp-l3vpn | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-tsvwg-rsvp-l3vpn | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Dr. Bruce S. Davie
François Le Faucheur
Ashok Narayanan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)