Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)
RFC 8356

Document Type RFC - Proposed Standard (March 2018; No errata)
Updates RFC 5440
Last updated 2018-03-06
Replaces draft-dhody-pce-pcep-exp-codepoints
Stream IETF
Formats plain text pdf html bibtex
Reviews GENART, SECDIR will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Jonathan Hardwick
Shepherd write-up Show (last changed 2017-11-12)
IESG IESG state RFC 8356 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Jonathan Hardwick <jonathan.hardwick@metaswitch.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          D. Dhody
Request for Comments: 8356                           Huawei Technologies
Updates: 5440                                                    D. King
Category: Standards Track                           Lancaster University
ISSN: 2070-1721                                                A. Farrel
                                                        Juniper Networks
                                                              March 2018

                 Experimental Codepoint Allocation for
       the Path Computation Element Communication Protocol (PCEP)

Abstract

   IANA assigns values to the Path Computation Element Communication
   Protocol (PCEP) parameters (messages, objects, TLVs).  IANA
   established a top-level registry to contain all PCEP codepoints and
   sub-registries.  This top-level registry contains sub-registries for
   PCEP message, object, and TLV types.  The allocation policy for each
   of these sub-registries is IETF Review.

   This document updates RFC 5440 by changing the allocation policies
   for these three registries to mark some of the codepoints as assigned
   for Experimental Use.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8356.

Dhody, et al.                Standards Track                    [Page 1]
RFC 8356            Experimental Codepoints for PECP          March 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Experimental PCEP Messages  . . . . . . . . . . . . . . . . .   3
   3.  Experimental PCEP Objects . . . . . . . . . . . . . . . . . .   4
   4.  Experimental PCEP TLVs  . . . . . . . . . . . . . . . . . . .   4
   5.  Handling of Unknown Experimentation . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  PCEP Messages . . . . . . . . . . . . . . . . . . . . . .   4
     6.2.  PCEP Objects  . . . . . . . . . . . . . . . . . . . . . .   5
     6.3.  PCEP TLVs . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Other PCEP Registries  . . . . . . . . . . . . . . .   7
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

Dhody, et al.                Standards Track                    [Page 2]
RFC 8356            Experimental Codepoints for PECP          March 2018

1.  Introduction

   The Path Computation Element Communication Protocol (PCEP) [RFC5440]
   provides mechanisms for Path Computation Elements (PCEs) to perform
   path computations in response to Path Computation Client (PCC)
   requests.

   Further, in order to support use cases described in [RFC8051],
Show full document text