[Pce] [Editorial Errata Reported] RFC8231 (6012)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 10 March 2020 02:39 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 F25EB3A0DA5 for <pce@ietfa.amsl.com>; Mon, 9 Mar 2020 19:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 CPIv1XNVno6e for <pce@ietfa.amsl.com>; Mon, 9 Mar 2020 19:39:50 -0700 (PDT)
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 3BEE03A0DA3 for <pce@ietf.org>; Mon, 9 Mar 2020 19:39:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8FB34F406D1; Mon, 9 Mar 2020 19:39:47 -0700 (PDT)
To: edward.crabbe@oracle.com, inaminei@google.com, jmedved@cisco.com, robert.varga@pantheon.tech, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, dhruv.ietf@gmail.com, julien.meuric@orange.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dhruv.ietf@gmail.com, pce@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200310023947.8FB34F406D1@rfc-editor.org>
Date: Mon, 09 Mar 2020 19:39:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/oTP4qUx98Y13f68jsPo33NnkXB8>
X-Mailman-Approved-At: Mon, 09 Mar 2020 19:43:03 -0700
Subject: [Pce] [Editorial Errata Reported] RFC8231 (6012)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 10 Mar 2020 02:39:52 -0000
The following errata report has been submitted for RFC8231, "Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6012 -------------------------------------- Type: Editorial Reported by: Dhruv Dhody <dhruv.ietf@gmail.com> Section: 5.8.3 Original Text ------------- If the PCC receives a PCUpd message for an LSP object identified with a PLSP-ID that does not exist on the PCC, it MUST generate a PCErr with Error-type=19 (Invalid Operation), error-value 3, (Attempted LSP Update Request for an LSP identified by an unknown PSP-ID) (see Section 8.5). Corrected Text -------------- If the PCC receives a PCUpd message for an LSP object identified with a PLSP-ID that does not exist on the PCC, it MUST generate a PCErr with Error-type=19 (Invalid Operation), error-value 3, (Attempted LSP Update Request for an LSP identified by an unknown PLSP-ID) (see Section 8.5). Notes ----- s/PSP-ID/PLSP-ID/ Thanks to Rebecca Vanrheenen from RFC Editor team for spotting this while editing another I-D. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8231 (draft-ietf-pce-stateful-pce-21) -------------------------------------- Title : Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE Publication Date : September 2017 Author(s) : E. Crabbe, I. Minei, J. Medved, R. Varga Category : PROPOSED STANDARD Source : Path Computation Element Area : Routing Stream : IETF Verifying Party : IESG
- [Pce] [Editorial Errata Reported] RFC8231 (6012) RFC Errata System