INTERNET-DRAFT                                        A. Farrel (Editor)
Network Working Group                                 Old Dog Consulting
Intended Status: Standards Track
Updates: RFC 3209, RFC 3473                                  A. Ayyangar
Expires: March 2008                                     Juniper Networks

                                                             JP. Vasseur
                                                     Cisco Systems, Inc.

                                                          September 2007

         Inter domain Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) Traffic Engineering - RSVP-TE extensions

              draft-ietf-ccamp-inter-domain-rsvp-te-07.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of 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.

Abstract

   This document describes procedures and protocol extensions for the
   use of Resource ReserVation Protocol Traffic Engineering (RSVP-TE)
   signaling in Multiprotocol Label Switching Traffic Engineering
   (MPLS-TE) packet networks and Generalized MPLS (GMPLS) packet and
   non-packet networks to support the establishment and maintenance of
   Label Switched Paths that cross domain boundaries.

   For the purpose of this document, a domain is considered to be any
   collection of network elements within a common realm of address space
   or path computation responsibility. Examples of such domains include
   Autonomous Systems, IGP routing areas, and GMPLS overlay networks.

Farrel, Ayyangar and Vasseur                                    [Page 1]

draft-ietf-ccamp-inter-domain-rsvp-te-07.txt              September 2007

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1   Conventions Used In This Document  . . . . . . . . . . . .  3
     1.2   Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Signaling Overview   . . . . . . . . . . . . . . . . . . . . .  4
     2.1   Signaling Options  . . . . . . . . . . . . . . . . . . . .  5
   3.  Procedures on the Domain Border Node . . . . . . . . . . . . .  6
     3.1   Rules on ERO Processing  . . . . . . . . . . . . . . . . .  7
     3.2   LSP Setup Failure and Crankback  . . . . . . . . . . . . .  9
     3.3   RRO Processing Across Domains  . . . . . . . . . . . . . . 10
     3.4   Notify Message Processing  . . . . . . . . . . . . . . . . 10
   4.  RSVP-TE Signaling Extensions . . . . . . . . . . . . . . . . . 11
     4.1   Control of Downstream Choice of Signaling Method . . . . . 11
   5.  Protection and Recovery of Inter-Domain TE LSPs  . . . . . . . 12
     5.1   Fast Recovery Support Using MPLS-TE Fast Reroute . . . . . 12
       5.1.1   Failure Within a Domain (Link or Node Failure) . . . . 13
       5.1.2   Failure of Link at Domain Borders  . . . . . . . . . . 13
       5.1.3   Failure of a Border Node . . . . . . . . . . . . . . . 13
     5.2   Protection and Recovery of GMPLS LSPs  . . . . . . . . . . 14
   6.  Re-Optimization of Inter-Domain TE LSPs  . . . . . . . . . . . 14
   7.  Backward Compatibility . . . . . . . . . . . . . . . . . . . . 16
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 16
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 18
     9.1   Attribute Flags for LSP_Attributes Object  . . . . . . . . 18
     9.2   New Error Codes  . . . . . . . . . . . . . . . . . . . . . 19
  10.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 19
  11.  References   . . . . . . . . . . . . . . . . . . . . . . . . . 19
      11.1   Normative References . . . . . . . . . . . . . . . . . . 19
      11.2   Informative References . . . . . . . . . . . . . . . . . 20
  12. Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . 21


1. Introduction

   The requirements for inter-area and inter-AS Multiprotocol Label
   Switching (MPLS) Traffic Engineering (TE) are stated in [RFC4105] and
   [RFC4216] respectively. Many of these requirements also apply to
   Generalized MPLS (GMPLS) networks. The framework for inter-domain
   MPLS-TE is provided in [