Path Computation Element communication Protocol extension for relationship between LSPs and Attributes
draft-dhody-pce-association-attr-06

Document Type Active Internet-Draft (individual)
Last updated 2017-03-12
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                               D. Dhody
Internet-Draft                                                     Q. Wu
Intended status: Standards Track                     Huawei Technologies
Expires: September 13, 2017                               March 12, 2017

     Path Computation Element communication Protocol extension for
                relationship between LSPs and Attributes
                  draft-dhody-pce-association-attr-06

Abstract

   The Path Computation Element (PCE) provides functions of path
   computation in support of traffic engineering in networks controlled
   by Multi-Protocol Label Switching (MPLS) and Generalized MPLS
   (GMPLS).

   This document defines a mechanism to create associations between a
   set of LSPs and a set of attributes (such as configuration
   parameters).

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 13, 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
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Dhody & Wu             Expires September 13, 2017               [Page 1]
Internet-Draft                 ASSOC-ATTR                     March 2017

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Opaque Identifier . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Bundled requests  . . . . . . . . . . . . . . . . . . . .   4
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Attribute Association Group . . . . . . . . . . . . . . . . .   5
     5.1.  ATTRIBUTE-OBJECT-TLV  . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Association object Type Indicators  . . . . . . . . . . .   8
     7.2.  PCEP TLV Type Indicators  . . . . . . . . . . . . . . . .   8
     7.3.  Flag field in ATTRIBUTE-OBJECT-TLV  . . . . . . . . . . .   8
   8.  Manageability Considerations  . . . . . . . . . . . . . . . .   8
     8.1.  Control of Function and Policy  . . . . . . . . . . . . .   9
     8.2.  Information and Data Models . . . . . . . . . . . . . . .   9
     8.3.  Liveness Detection and Monitoring . . . . . . . . . . . .   9
     8.4.  Verify Correct Operations . . . . . . . . . . . . . . . .   9
     8.5.  Requirements On Other Protocols . . . . . . . . . . . . .   9
     8.6.  Impact On Network Operations  . . . . . . . . . . . . . .   9
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Policy . . . . . . . . . . . . . . . . . . . . . . .  12
   Appendix B.  Contributor Addresses  . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   [RFC5440] describes the Path Computation Element communication
   Protocol (PCEP) which enables the communication between a Path
   Computation Client (PCC) and a Path Control Element (PCE), or between
   two PCEs based on the PCE architecture [RFC4655].

   [I-D.ietf-pce-association-group] introduces a generic mechanism to
Show full document text