[Pce] RFC 8356 on Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)
rfc-editor@rfc-editor.org Wed, 07 March 2018 06:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8532B127058; Tue, 6 Mar 2018 22:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyNPLGecViPd; Tue, 6 Mar 2018 22:04:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F9C9124BE8; Tue, 6 Mar 2018 22:04:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4BDE2B80C8E; Tue, 6 Mar 2018 22:03:47 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180307060347.4BDE2B80C8E@rfc-editor.org>
Date: Tue, 06 Mar 2018 22:03:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/dTbmBeQQdAnst7k8MbpfOoPaZ8w>
Subject: [Pce] RFC 8356 on Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2018 06:04:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8356
Title: Experimental Codepoint Allocation for the
Path Computation Element Communication Protocol (PCEP)
Author: D. Dhody,
D. King,
A. Farrel
Status: Standards Track
Stream: IETF
Date: March 2018
Mailbox: dhruv.ietf@gmail.com,
d.king@lancaster.ac.uk,
afarrel@juniper.net
Pages: 7
Characters: 14283
Updates: RFC 5440
I-D Tag: draft-ietf-pce-pcep-exp-codepoints-05.txt
URL: https://www.rfc-editor.org/info/rfc8356
DOI: 10.17487/RFC8356
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.
This document is a product of the Path Computation Element Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC