PCEP Extension for Transporting TE Data
draft-dhodylee-pce-pcep-te-data-extn-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-27
Replaced by draft-dhodylee-pce-pcep-ls
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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                                               D. Dhody
Internet-Draft                                                    Y. Lee
Intended status: Standards Track                     Huawei Technologies
Expires: April 30, 2015                                    D. Ceccarelli
                                                                Ericsson
                                                        October 27, 2014

                PCEP Extension for Transporting TE Data
                draft-dhodylee-pce-pcep-te-data-extn-01

Abstract

   In order to compute and provide optimal paths, Path Computation
   Elements (PCEs) require an accurate and timely Traffic Engineering
   Database (TED).  Traditionally this TED has been obtained from a link
   state routing protocol supporting traffic engineering extensions.

   This document extends the Path Computation Element Communication
   Protocol (PCEP) with TED population capability.

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 April 30, 2015.

Copyright Notice

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

Dhody, et al.            Expires April 30, 2015                 [Page 1]
Internet-Draft                PCEP-TED-EXT                  October 2014

   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 . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Requirements for PCEP extension . . . . . . . . . . . . . . .   4
   5.  New Functions to Support TED via PCEP . . . . . . . . . . . .   5
   6.  Overview of Extension to PCEP . . . . . . . . . . . . . . . .   5
     6.1.  New Messages  . . . . . . . . . . . . . . . . . . . . . .   5
     6.2.  Capability Advertisement  . . . . . . . . . . . . . . . .   6
     6.3.  Initial TED Synchronization . . . . . . . . . . . . . . .   6
       6.3.1.  Optimizations for TED Synchronization . . . . . . . .   9
     6.4.  TE Report . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Transport . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  PCEP Messages . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  TE Report Message . . . . . . . . . . . . . . . . . . . .  10
     8.2.  The PCErr Message . . . . . . . . . . . . . . . . . . . .  10
   9.  Objects and TLV . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Open Object . . . . . . . . . . . . . . . . . . . . . . .  11
       9.1.1.  TED Capability TLV  . . . . . . . . . . . . . . . . .  11
     9.2.  TE Object . . . . . . . . . . . . . . . . . . . . . . . .  12
       9.2.1.  Routing Universe TLV  . . . . . . . . . . . . . . . .  13
       9.2.2.  Local TE Node Descriptors TLV . . . . . . . . . . . .  14
       9.2.3.  Remote TE Node Descriptors TLV  . . . . . . . . . . .  15
       9.2.4.  TE Node Descriptors Sub-TLVs  . . . . . . . . . . . .  15
       9.2.5.  TE Link Descriptors TLV . . . . . . . . . . . . . . .  16
       9.2.6.  TE Node Attributes TLV  . . . . . . . . . . . . . . .  17
       9.2.7.  TE Link Attributes TLV  . . . . . . . . . . . . . . .  18
   10. Other Considerations  . . . . . . . . . . . . . . . . . . . .  20
     10.1.  Inter-AS Links . . . . . . . . . . . . . . . . . . . . .  20
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  20
   12. Manageability Considerations  . . . . . . . . . . . . . . . .  20
     12.1.  Control of Function and Policy . . . . . . . . . . . . .  20
     12.2.  Information and Data Models  . . . . . . . . . . . . . .  20
     12.3.  Liveness Detection and Monitoring  . . . . . . . . . . .  20
Show full document text