Skip to main content

Requirements for supporting Customer RSVP and RSVP-TE Over a BGP/MPLS IP-VPN

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Kenji Kumaki
Last updated 2010-01-15 (Latest revision 2008-02-20)
Replaced by draft-ietf-l3vpn-e2e-rsvp-te-reqts
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-l3vpn-e2e-rsvp-te-reqts
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:


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


Kenji Kumaki

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)