PCEP extensions for GMPLS
draft-ietf-pce-gmpls-pcep-extensions-12

Document Type Active Internet-Draft (pce WG)
Last updated 2018-11-27 (latest revision 2018-09-27)
Replaces draft-margaria-pce-gmpls-pcep-extensions
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Sep 2013 - Submit PCEP extensio... )
Document shepherd Julien Meuric
Shepherd write-up Show (last changed 2018-10-01)
IESG IESG state Waiting for AD Go-Ahead::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Julien Meuric <julien.meuric@orange.com>
IANA IANA review state IANA - Not OK
IANA action state None
Network Working Group                                   C. Margaria, Ed.
Internet-Draft                                                   Juniper
Intended status: Standards Track                O. Gonzalez de Dios, Ed.
Expires: March 31, 2019            Telefonica Investigacion y Desarrollo
                                                           F. Zhang, Ed.
                                                     Huawei Technologies
                                                      September 27, 2018

                       PCEP extensions for GMPLS
                draft-ietf-pce-gmpls-pcep-extensions-12

Abstract

   This memo provides extensions to the Path Computation Element
   communication Protocol (PCEP) for the support of GMPLS control plane.

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 https://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 March 31, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

Margaria, et al.         Expires March 31, 2019                 [Page 1]
Internet-Draft             PCEP Ext for GMPLS             September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Contributing Authors  . . . . . . . . . . . . . . . . . .   3
     1.2.  PCEP Requirements for GMPLS . . . . . . . . . . . . . . .   3
     1.3.  Current GMPLS Support and Limitation of Base PCEP Objects   4
     1.4.  Requirements Language . . . . . . . . . . . . . . . . . .   5
   2.  PCEP Objects and Extensions . . . . . . . . . . . . . . . . .   6
     2.1.  GMPLS Capability Advertisement  . . . . . . . . . . . . .   6
       2.1.1.  GMPLS Computation TLV in the Existing PCE Discovery
               Protocol  . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  OPEN Object Extension GMPLS-CAPABILITY TLV  . . . . .   6
     2.2.  RP Object Extension . . . . . . . . . . . . . . . . . . .   7
     2.3.  BANDWIDTH Object Extensions . . . . . . . . . . . . . . .   7
     2.4.  LOAD-BALANCING Object Extensions  . . . . . . . . . . . .  10
     2.5.  END-POINTS Object Extensions  . . . . . . . . . . . . . .  11
       2.5.1.  Generalized Endpoint Object Type  . . . . . . . . . .  12
       2.5.2.  END-POINTS TLV Extensions . . . . . . . . . . . . . .  15
     2.6.  IRO Extension . . . . . . . . . . . . . . . . . . . . . .  18
     2.7.  XRO Extension . . . . . . . . . . . . . . . . . . . . . .  18
     2.8.  LSPA Extensions . . . . . . . . . . . . . . . . . . . . .  20
     2.9.  NO-PATH Object Extension  . . . . . . . . . . . . . . . .  20
       2.9.1.  Extensions to NO-PATH-VECTOR TLV  . . . . . . . . . .  21
   3.  Additional Error-Types and Error-Values Defined . . . . . . .  21
   4.  Manageability Considerations  . . . . . . . . . . . . . . . .  23
     4.1.  Control of Function through Configuration and Policy  . .  23
     4.2.  Information and Data Models . . . . . . . . . . . . . . .  23
     4.3.  Liveness Detection and Monitoring . . . . . . . . . . . .  23
     4.4.  Verifying Correct Operation . . . . . . . . . . . . . . .  24
     4.5.  Requirements on Other Protocols and Functional Components  24
     4.6.  Impact on Network Operation . . . . . . . . . . . . . . .  24
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  24
     5.1.  PCEP Objects  . . . . . . . . . . . . . . . . . . . . . .  24
     5.2.  END-POINTS Object, Object Type Generalized Endpoint . . .  25
     5.3.  New PCEP TLVs . . . . . . . . . . . . . . . . . . . . . .  26
     5.4.  RP Object Flag Field  . . . . . . . . . . . . . . . . . .  26
     5.5.  New PCEP Error Codes  . . . . . . . . . . . . . . . . . .  27
     5.6.  New NO-PATH-VECTOR TLV Fields . . . . . . . . . . . . . .  28
     5.7.  New Subobject for the Include Route Object  . . . . . . .  28
Show full document text