Static PCEP Link State
draft-chen-pce-pcc-ted-02

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
PCE Working Group                                                H. Chen
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                                  M. Toy
Expires: September 14, 2017                                      Verizon
                                                                  X. Liu
                                                                   Jabil
                                                                  L. Liu
                                                                 Fujitsu
                                                                   Z. Li
                                                            China Mobile
                                                          March 13, 2017

                         Static PCEP Link State
                       draft-chen-pce-pcc-ted-02

Abstract

   This document presents extensions to the Path Computation Element
   Communication Protocol (PCEP) for a PCC to advertise the information
   about the links without running IGP and for a PCE to build a TED
   based on the information received.

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 September 14, 2017.

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

Chen, et al.           Expires September 14, 2017               [Page 1]
Internet-Draft                   PCE-TED                      March 2017

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Conventions Used in This Document . . . . . . . . . . . . . .   3
   4.  Link Information  . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Extensions to PCEP  . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Extension to Existing Message . . . . . . . . . . . . . .   4
       5.1.1.  TLVs  . . . . . . . . . . . . . . . . . . . . . . . .   4
       5.1.2.  Sub-TLVs  . . . . . . . . . . . . . . . . . . . . . .   5
     5.2.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   6
       5.2.1.  PCC Procedures  . . . . . . . . . . . . . . . . . . .   6
       5.2.2.  PCE Procedures  . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  New Message  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   A PCE architecture is described in RFC 4655, in which a Traffic
   Engineering Database (TED) for a PCE is constructed based on the link
   information from IGP (OSPF or IS-IS) running in the domain for which
   the PCE is responsible.

   For a domain without running IGP, the PCE responsible for the domain
   may obtain the link information from a PCC running on each node in
   the domain.

   This document presents extensions to the Path Computation Element
   Communication Protocol (PCEP) for a PCC to advertise the information
   about the links attached to the node running the PCC and for a PCE to
   build the TED based on the information received from the PCC.
Show full document text