Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
RFC 5824
Internet Engineering Task Force (IETF) K. Kumaki, Ed.
Request for Comments: 5824 KDDI Corporation
Category: Informational R. Zhang
ISSN: 2070-1721 BT
Y. Kamite
NTT Communications Corporation
April 2010
Requirements for Supporting
Customer Resource ReSerVation Protocol (RSVP)
and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
Abstract
Today, customers expect to run triple-play services through BGP/MPLS
IP-VPNs. Some service providers will deploy services that request
Quality of Service (QoS) guarantees from a local Customer Edge (CE)
to a remote CE across the network. As a result, the application
(e.g., voice, video, bandwidth-guaranteed data pipe, etc.)
requirements for an end-to-end QoS and reserving an adequate
bandwidth continue to increase.
Service providers can use both an MPLS and an MPLS Traffic
Engineering (MPLS-TE) Label Switched Path (LSP) to meet their service
objectives. This document describes service-provider requirements
for supporting a customer Resource ReSerVation Protocol (RSVP) and
RSVP-TE over a BGP/MPLS IP-VPN.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5824.
Kumaki, et al. Informational [Page 1]
RFC 5824 Supporting RSVP/RSVP-TE over BGP/MPLS IP-VPN April 2010
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Kumaki, et al. Informational [Page 2]
RFC 5824 Supporting RSVP/RSVP-TE over BGP/MPLS IP-VPN April 2010
Table of Contents
1. Introduction ....................................................4
2. Requirements Language ...........................................4
3. Terminology .....................................................5
4. Problem Statement ...............................................5
5. Application Scenarios ...........................................7
5.1. Scenario I: Fast Recovery over BGP/MPLS IP-VPNs ............8
5.2. Scenario II: Strict C-TE LSP QoS Guarantees ................8
5.3. Scenario III: Load Balance of CE-to-CE Traffic .............9
5.4. Scenario IV: RSVP Aggregation over MPLS-TE Tunnels ........11
5.5. Scenario V: RSVP over Non-TE LSPs .........................12
5.6. Scenario VI: RSVP-TE over Non-TE LSPs .....................13
6. Detailed Requirements for C-TE LSP Model .......................14
6.1. Selective P-TE LSPs .......................................14
Show full document text