Requirements for supporting Customer RSVP and RSVP-TE Over a BGP/MPLS IP-VPN
draft-kumaki-l3vpn-e2e-rsvp-te-reqts-06

Document Type Replaced Internet-Draft (individual)
Last updated 2010-01-15 (latest revision 2008-02-20)
Replaced by draft-ietf-l3vpn-e2e-rsvp-te-reqts
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
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
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kumaki-l3vpn-e2e-rsvp-te-reqts-06.txt

Abstract

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

Authors

Kenji Kumaki (ke-kumaki@kddi.com)

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