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

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Last updated 2012-05-22
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
PCE Working Group                                               D. Dhody
Internet-Draft                                                  U. Palle
Intended status: Experimental              Huawei Technologies India Pvt
Expires: November 23, 2012                                           Ltd
                                                             R. Casellas
                                             CTTC - Centre Tecnologic de
                                          Telecomunicacions de Catalunya
                                                            May 22, 2012

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

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 for P2P and P2MP scenarios.  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 IGP area or an Autonomous Systems.  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.  This document also
   defines new sub-objects 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 November 23, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Dhody, et al.           Expires November 23, 2012               [Page 1]
Internet-Draft                 DOMAIN SEQ                       May 2012

   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  . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Detail Description . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Domains  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.2.  Domain-Sequence  . . . . . . . . . . . . . . . . . . . . .  5
     3.3.  Standard Representation  . . . . . . . . . . . . . . . . .  6
     3.4.  Mode of Operation  . . . . . . . . . . . . . . . . . . . .  8
     3.5.  Examples . . . . . . . . . . . . . . . . . . . . . . . . .  9
       3.5.1.  Inter-Area Path Computation  . . . . . . . . . . . . .  9
       3.5.2.  Inter-AS Path Computation  . . . . . . . . . . . . . . 11
         3.5.2.1.  Example 1  . . . . . . . . . . . . . . . . . . . . 11
         3.5.2.2.  Example 2  . . . . . . . . . . . . . . . . . . . . 13
       3.5.3.  Boundary Node and Inter-AS-Link  . . . . . . . . . . . 15
       3.5.4.  PCE serving multiple domains . . . . . . . . . . . . . 16
       3.5.5.  P2MP . . . . . . . . . . . . . . . . . . . . . . . . . 16
       3.5.6.  HPCE . . . . . . . . . . . . . . . . . . . . . . . . . 16
       3.5.7.  Relationship to PCE Sequence . . . . . . . . . . . . . 18
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 19
     4.1.  New IRO Object Type  . . . . . . . . . . . . . . . . . . . 19
     4.2.  Sub-Objects  . . . . . . . . . . . . . . . . . . . . . . . 19
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   6.  Manageability Considerations . . . . . . . . . . . . . . . . . 19
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 19
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 19
Show full document text