Support for RSVP-TE in L3VPNs
draft-kumaki-murai-l3vpn-rsvp-te-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2011-10-30 (latest revision 2011-09-01)
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     K. Kumaki, Ed.
Internet Draft                                          KDDI Corporation
Intended Status: Standards Track                                T. Murai
Expires: April 30, 2012                 Furukawa Network Solutions Corp.
                                                                D. Cheng
                                                     Huawei Technologies
                                                           S. Matsushima
                                                        Softbank Telecom
                                                                P. Jiang
                                                           KDDI R&D Labs
                                                        October 30, 2011

                       Support for RSVP-TE in L3VPNs
                  draft-kumaki-murai-l3vpn-rsvp-te-04.txt

Abstract

   IP Virtual Private Networks (VPNs) provide connectivity between sites
   across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
   and a single provider edge (PE) node may provide access to multiple 
   customer sites belonging to different VPNs.

   The VPNs may support a number of customer services including RSVP and
   RSVP-TE traffic. This document describes how to support RSVP-TE  
   between customer sites when a single PE supports multiple VPNs. 

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on April xx, 2012.

K.Kumaki, et al.                                              [Page 1]
draft-kumaki-murai-l3vpn-rsvp-te-04                       October 2011

Copyright Notice

   Copyright (c) 2011 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.

Table of Contents

   1. Introduction..................................................3
   2. Motivation....................................................3
      2.1 Network Example...........................................3
   3. Protocol Extensions and Procedures............................5
      3.1 Object Definitions........................................5
      3.1.1 LSP_TUNNEL_VPN-IPv4 and LSP_TUNNEL_VPN-IPv6 SESSION Object
      ..............................................................5
      3.1.2 LSP_TUNNEL_VPN-IPv4 and LSP_TUNNEL_VPN-IPv6 SENDER_TEMPLATE
      Objects.......................................................7
      3.1.3 LSP_TUNNEL_VPN-IPv4 and LSP_TUNNEL_VPN-IPv6 FILTER_SPEC
      Objects.......................................................8
      3.1.4 VPN-IPv4 and VPN-IPv6 RSVP_HOP Objects..................8
      3.2 Handling..................................................8
      3.2.1 Path Message Processing at Ingress PE...................8
      3.2.2 Path Message Processing at Egress PE....................9
      3.2.3 Resv Processing at Egress PE............................10
      3.2.4 Resv Processing at Ingress PE...........................10
      3.2.5 Other RSVP Messages.....................................11
   4. Management Considerations.....................................11
      4.1 Impact on Network Operation...............................11
   5. Security Considerations.......................................11
   6. IANA Considerations...........................................12
   7. References....................................................12
      7.1 Normative References......................................12
Show full document text