Experimental Codepoint Allocation for the Path Computation Element communication Protocol (PCEP)
draft-ietf-pce-pcep-exp-codepoints-04
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (pce WG) | |
Authors | Dhruv Dhody , Daniel King , Adrian Farrel | ||
Last updated | 2017-12-28 (latest revision 2017-11-27) | ||
Replaces | draft-dhody-pce-pcep-exp-codepoints | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jonathan Hardwick | ||
Shepherd write-up | Show (last changed 2017-11-12) | ||
IESG | IESG state | Waiting for AD Go-Ahead | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs 6 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Deborah Brungard | ||
Send notices to | Jonathan Hardwick <jonathan.hardwick@metaswitch.com> | ||
IANA | IANA review state | IANA OK - Actions Needed |
PCE Working Group D. Dhody Internet-Draft Huawei Technologies Updates: 5440 (if approved) D. King Intended status: Standards Track Lancaster University Expires: May 31, 2018 A. Farrel Juniper Networks November 27, 2017 Experimental Codepoint Allocation for the Path Computation Element communication Protocol (PCEP) draft-ietf-pce-pcep-exp-codepoints-04 Abstract IANA assigns values to the Path Computation Element (PCE) 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 code points as assigned for Experimental Use. 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 https://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 May 31, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. Dhody, et al. Expires May 31, 2018 [Page 1] Internet-Draft EXP-CODEPOINT November 2017 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 2. PCEP Messages . . . . . . . . . . . . . . . . . . . . . . . . 3 3. PCEP Objects . . . . . . . . . . . . . . . . . . . . . . . . 3 4. PCEP TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Handling of Unknown Experimentation . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6.1. New PCEP Messages . . . . . . . . . . . . . . . . . . . . 4 6.2. New PCEP Objects . . . . . . . . . . . . . . . . . . . . 4 6.3. New PCEP TLVs . . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 9.2. Informative References . . . . . . . . . . . . . . . . . 6 Appendix A. Other PCEP Registries . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 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 Clients (PCCs) requests. Dhody, et al. Expires May 31, 2018 [Page 2]Show full document text