datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Standard Representation Of Domain-Sequence
draft-ietf-pce-pcep-domain-sequence-04

Document type: Active Internet-Draft (pce WG)
Document stream: IETF
Last updated: 2014-01-07
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

PCE Working Group                                               D. Dhody
Internet-Draft                                                  U. Palle
Intended status: Experimental                        Huawei Technologies
Expires: July 11, 2014                                       R. Casellas
                                                                    CTTC
                                                         January 7, 2014

               Standard Representation Of Domain-Sequence
                 draft-ietf-pce-pcep-domain-sequence-04

Abstract

   The ability to compute shortest constrained Traffic Engineering Label
   Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) networks across multiple domains has been
   identified as a key requirement.  In this context, a domain is a
   collection of network elements within a common sphere of address
   management or path computational responsibility such as an Interior
   Gateway Protocol (IGP) area or an Autonomous Systems (AS).  This
   document specifies a standard representation and encoding of a
   Domain-Sequence, which is defined as an ordered sequence of domains
   traversed to reach the destination domain to be used by Path
   Computation Elements (PCEs) to compute inter-domain shortest
   constrained paths across a predetermined sequence of domains . This
   document also defines new subobjects to be used to encode domain
   identifiers.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on July 11, 2014.

Dhody, et al.             Expires July 11, 2014                 [Page 1]
Internet-Draft                 DOMAIN SEQ                   January 2014

Copyright Notice

   Copyright (c) 2014 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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Detail Description  . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Domains . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Domain-Sequence . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Standard Representation . . . . . . . . . . . . . . . . .   6
     3.4.  Include Route Object (IRO)  . . . . . . . . . . . . . . .   7
       3.4.1.  Subobjects  . . . . . . . . . . . . . . . . . . . . .   7
       3.4.2.  Option (A): New IRO Object Type . . . . . . . . . . .   9
         3.4.2.1.  Handling of the Domain-Sequence IRO object  . . .  11
       3.4.3.  Option B: Existing IRO Object Type  . . . . . . . . .  12
       3.4.4.  Comparison  . . . . . . . . . . . . . . . . . . . . .  13
     3.5.  Exclude Route Object (XRO)  . . . . . . . . . . . . . . .  14
       3.5.1.  Subobjects  . . . . . . . . . . . . . . . . . . . . .  14
         3.5.1.1.  Autonomous system . . . . . . . . . . . . . . . .  14
         3.5.1.2.  IGP Area  . . . . . . . . . . . . . . . . . . . .  15
     3.6.  Explicit Exclusion Route Subobject (EXRS) . . . . . . . .  16
     3.7.  Explicit Route Object (ERO) . . . . . . . . . . . . . . .  17
   4.  Other Considerations  . . . . . . . . . . . . . . . . . . . .  17
     4.1.  Inter-Area Path Computation . . . . . . . . . . . . . . .  18
     4.2.  Inter-AS Path Computation . . . . . . . . . . . . . . . .  20
       4.2.1.  Example 1 . . . . . . . . . . . . . . . . . . . . . .  20
       4.2.2.  Example 2 . . . . . . . . . . . . . . . . . . . . . .  22
     4.3.  Boundary Node and Inter-AS-Link . . . . . . . . . . . . .  24

[include full document text]