Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs
RFC 6016

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 07

Internet Engineering Task Force (IETF)                          B. Davie
Request for Comments: 6016                                F. Le Faucheur
Category: Standards Track                                   A. Narayanan
ISSN: 2070-1721                                      Cisco Systems, Inc.
                                                            October 2010

  Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs

Abstract

   RFC 4364 and RFC 4659 define an approach to building provider-
   provisioned Layer 3 VPNs (L3VPNs) for IPv4 and IPv6.  It may be
   desirable to use Resource Reservation Protocol (RSVP) to perform
   admission control on the links between Customer Edge (CE) routers and
   Provider Edge (PE) routers.  This document specifies procedures by
   which RSVP messages traveling 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.

Status of This Memo

   This is an Internet Standards Track document.

   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).  Further information on
   Internet Standards is available in 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/rfc6016.

Davie, et al.                Standards Track                    [Page 1]
RFC 6016                     RSVP for L3VPNs                October 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.

Davie, et al.                Standards Track                    [Page 2]
RFC 6016                     RSVP for L3VPNs                October 2010

Table of Contents

   1. Introduction ....................................................4
      1.1. Terminology ................................................5
      1.2. Requirements Language ......................................5
   2. Problem Statement ...............................................5
      2.1. Model of Operation .........................................8
   3. Admission Control on PE-CE Links ................................9
      3.1. New Objects of Type VPN-IPv4 ...............................9
      3.2. Path Message Processing at Ingress PE .....................11
      3.3. Path Message Processing at Egress PE ......................12
      3.4. Resv Processing at Egress PE ..............................13
      3.5. Resv Processing at Ingress PE .............................13
      3.6. Other RSVP Messages .......................................14
   4. Admission Control in Provider's Backbone .......................14
   5. Inter-AS Operation .............................................15
      5.1. Inter-AS Option A .........................................15
      5.2. Inter-AS Option B .........................................15
           5.2.1. Admission Control on ASBR ..........................16
           5.2.2. No Admission Control on ASBR .......................16
      5.3. Inter-AS Option C .........................................17
   6. Operation with RSVP Disabled ...................................17
   7. Other RSVP Procedures ..........................................18
      7.1. Refresh Overhead Reduction ................................18