BGP Extensions for Path Computation Element (PCE) Discovery
draft-dong-pce-discovery-proto-bgp-07

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
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)
Network Working Group                                            J. Dong
Internet-Draft                                                   M. Chen
Intended status: Standards Track                                D. Dhody
Expires: January 4, 2018                             Huawei Technologies
                                                             J. Tantsura
                                                              Individual
                                                               K. Kumaki
                                                        KDDI Corporation
                                                                T. Murai
                                         Furukawa Network Solution Corp.
                                                            July 3, 2017

      BGP Extensions for Path Computation Element (PCE) Discovery
                 draft-dong-pce-discovery-proto-bgp-07

Abstract

   In networks where a Path Computation Element (PCE) is used for path
   computation, it is desirable for the Path Computation Clients (PCCs)
   to discover dynamically and automatically a set of PCEs along with
   certain information relevant for PCE selection.  RFC 5088 and RFC
   5089 define the PCE discovery mechanisms based on Interior Gateway
   Protocols (IGP).  This document defines extensions to BGP for the
   advertisement of PCE Discovery information.  The BGP based PCE
   discovery mechanism is complementary to the existing IGP based
   mechanisms.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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

Dong, et al.             Expires January 4, 2018                [Page 1]
Internet-Draft      BGP Extensions for PCE Discovery           July 2017

   This Internet-Draft will expire on January 4, 2018.

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Carrying PCE Discovery Information in BGP . . . . . . . . . .   3
     2.1.  PCE NLRI  . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  PCE Descriptors . . . . . . . . . . . . . . . . . . .   4
     2.2.  PCE Attribute TLVs  . . . . . . . . . . . . . . . . . . .   5
       2.2.1.  PCE Domain TLV  . . . . . . . . . . . . . . . . . . .   6
       2.2.2.  Neighbor PCE Domain TLV . . . . . . . . . . . . . . .   6
   3.  Operational Considerations  . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   In networks where a Path Computation Element (PCE) is used for path
   computation, it is desirable for the Path Computation Clients (PCCs)
   to discover dynamically and automatically a set of PCEs along with
Show full document text