Extensions to PCEP for Distributing Label Cross Domains
draft-chen-pce-label-x-domains-05

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                  H. Chen
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                                  A. Liu
Expires: May 4, 2017                                            Ericsson
                                                                   F. Xu
                                                                 Verizon
                                                                  M. Toy
                                                                 Comcast
                                                                  V. Liu
                                                            China Mobile
                                                        October 31, 2016

        Extensions to PCEP for Distributing Label Cross Domains
                 draft-chen-pce-label-x-domains-05.txt

Abstract

   This document specifies extensions to PCEP for distributing labels
   crossing domains for an inter-domain Point-to-Point (P2P) or Point-
   to-Multipoint (P2MP) Traffic Engineering (TE) Label Switched Path
   (LSP).

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 May 4, 2017.

Copyright Notice

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

Chen, et al.               Expires May 4, 2017                  [Page 1]
Internet-Draft             Label Cross Domains              October 2016

   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.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Conventions Used in This Document  . . . . . . . . . . . . . .  4
   4.  Label Distribution . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  An Exmaple . . . . . . . . . . . . . . . . . . . . . . . .  4
   5.  Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . .  5
     5.1.  RP Object Extension  . . . . . . . . . . . . . . . . . . .  5
     5.2.  Label Object . . . . . . . . . . . . . . . . . . . . . . .  6
     5.3.  LSP Tunnel Object  . . . . . . . . . . . . . . . . . . . .  7
     5.4.  Request Message Extension  . . . . . . . . . . . . . . . .  9
     5.5.  Reply Message Extension  . . . . . . . . . . . . . . . . .  9
   6.  Security  Considerations . . . . . . . . . . . . . . . . . . .  9
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
     7.1.  Request Parameter Bit Flags  . . . . . . . . . . . . . . . 10
   8.  Acknowledgement  . . . . . . . . . . . . . . . . . . . . . . . 10
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Chen, et al.               Expires May 4, 2017                  [Page 2]
Internet-Draft             Label Cross Domains              October 2016

1.  Introduction

   After a path crossing multiple domains is computed, an inter-domain
   Traffic Engineering (TE) Label Switched Path (LSP) tunnel may be set
   up along the path by a number of tunnel central controllers (TCCs).
   Each of the domains through which the path goes may be controlled by
   a tunnel central controller (TCC), which sets up the segment of the
   TE LSP tunnel in the domain.  When the TCC sets up the segment of the
   TE LSP tunnel in its domain that is not a domain containing the tail
Show full document text