[Pce] [Errata Verified] RFC5440 (4956)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 02 March 2017 21:22 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 51A0B129653; Thu, 2 Mar 2017 13:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 gI3xRe41jbps; Thu, 2 Mar 2017 13:22:49 -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 15549120724; Thu, 2 Mar 2017 13:22:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0A2ECB8204F; Thu, 2 Mar 2017 13:22:49 -0800 (PST)
To: afarrel@juniper.net, jpv@cisco.com, jeanlouis.leroux@orange-ftgroup.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20170302212249.0A2ECB8204F@rfc-editor.org>
Date: Thu, 02 Mar 2017 13:22:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/f0F9-9-7hiGmrW9amHTg_Mtl57Y>
Cc: text/plain@rfc-editor.org, charset=UTF-8@rfc-editor.org, rfc-editor@rfc-editor.orgContent-Type, pce@ietf.org, iesg@ietf.org
Subject: [Pce] [Errata Verified] RFC5440 (4956)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 02 Mar 2017 21:22:50 -0000
The following errata report has been verified for RFC5440, "Path Computation Element (PCE) Communication Protocol (PCEP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5440&eid=4956 -------------------------------------- Status: Verified Type: Editorial Reported by: Adrian Farrel <afarrel@juniper.net> Date Reported: 2017-03-01 Verified by: Deborah Brungard (IESG) Section: 9.3 Original Text ------------- Corrected Text -------------- Notes ----- This section does not tell IANA the range for the Object-Types to be registered for each Object-Class, nor what to do with the values not assigned in this document. IANA has correctly recognised that the top value is 15, and that the values between those shown here and 15 should be marked as "Unassigned." However, there is confusion over the value 0 for an Object-Type. The old entries (arising from RFC 5440) do not mention 0. Newer entries for RFC 7470 and several I-Ds in the pipe mark 0 as Unassigned. For consistency, ALL 0 Object-Types should be marked "Reserved". (This might need an Errata Report against some other RFCs if you are particularly fussy, but I think we can do it all on this report.) -------------------------------------- RFC5440 (draft-ietf-pce-pcep-19) -------------------------------------- Title : Path Computation Element (PCE) Communication Protocol (PCEP) Publication Date : March 2009 Author(s) : JP. Vasseur, Ed., JL. Le Roux, Ed. Category : PROPOSED STANDARD Source : Path Computation Element Area : Routing Stream : IETF Verifying Party : IESG
- [Pce] [Errata Verified] RFC5440 (4956) RFC Errata System