Experimental Codepoint Allocation for Path Computation Element communication Protocol (PCEP)
draft-dhody-pce-pcep-exp-codepoints-02

Document Type Active Internet-Draft (individual)
Last updated 2016-12-08
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                                       Huawei Technologies
Intended status: Standards Track                                 D. King
Expires: June 11, 2017                              Lancaster University
                                                        December 8, 2016

     Experimental Codepoint Allocation for Path Computation Element
                     communication Protocol (PCEP)
                 draft-dhody-pce-pcep-exp-codepoints-02

Abstract

   IANA assigns values to the Path Computation Element (PCE)
   communication Protocol (PCEP) parameters (messages, objects, TLVs).
   IANA established a new top-level registry to contain all PCEP
   codepoints and sub-registries.  The allocation policy for each new
   registry is by IETF Consensus.

   This document seeks to mark some codepoints for experimental usage of
   PCEP.

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 June 11, 2017.

Copyright Notice

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

Dhody & King              Expires June 11, 2017                 [Page 1]
Internet-Draft                EXP-CODEPOINT                December 2016

   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.  PCEP Messages . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  PCEP Objects  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  PCEP TLVs . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  New PCEP Messages . . . . . . . . . . . . . . . . . . . .   3
     5.2.  New PCEP Objects  . . . . . . . . . . . . . . . . . . . .   3
     5.3.  New PCEP TLVs . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Allocation Policy . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Other Codepoints . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Path Computation Element communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.

   In section 9 of [RFC5440], IANA assigns values to the PCEP protocol
   parameters (messages, objects, TLVs).  IANA established a new top-
   level registry to contain all PCEP codepoints and sub-registries.
   The allocation policy for each new registry is by IETF Consensus as
   described in [RFC5226].  Specifically, new assignments are made via
   RFCs approved by the IESG.  Typically, the IESG will seek input on
   prospective assignments from appropriate persons (e.g., a relevant
   Working Group if one exists).  Early allocation [RFC7120] provides
   some latitude for allocation of these code points, but is reserved
   for features that are considered appropriately stable.

   With some recent advancement, there is an enhanced need to experiment
   with PCEP.  It is often necessary to use some sort of number or
   constant in order to actually test or experiment with the new
Show full document text