[Pce] [Technical Errata Reported] RFC8231 (6231)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 13 July 2020 21:18 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 3BABC3A0B6B for <pce@ietfa.amsl.com>; Mon, 13 Jul 2020 14:18:39 -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 dlDPpFI3q7pv for <pce@ietfa.amsl.com>; Mon, 13 Jul 2020 14:18:38 -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 2715F3A0858 for <pce@ietf.org>; Mon, 13 Jul 2020 14:18:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D95B6F4074C; Mon, 13 Jul 2020 14:18:07 -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, dd@dhruvdhody.com, julien.meuric@orange.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dd@dhruvdhody.com, pce@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200713211807.D95B6F4074C@rfc-editor.org>
Date: Mon, 13 Jul 2020 14:18:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/q5ietsm6UFaM2f7Yjcx6FbxCmV4>
X-Mailman-Approved-At: Mon, 13 Jul 2020 14:20:11 -0700
Subject: [Pce] [Technical Errata Reported] RFC8231 (6231)
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: Mon, 13 Jul 2020 21:18:39 -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/eid6231

--------------------------------------
Type: Technical
Reported by: Dhruv Dhody <dd@dhruvdhody.com>

Section: 8.5

Original Text
-------------
      20       LSP State Synchronization Error

                Error-value
                1:   A PCE indicates to a PCC that it cannot process (an
                     otherwise valid) LSP State Report.  The PCEP-ERROR
                     object is followed by the LSP object that
                     identifies the LSP.

Corrected Text
--------------
      20       LSP State Synchronization Error

                Error-value
                1:   A PCE indicates to a PCC that it cannot process (an
                     otherwise valid) LSP State Report.  

Notes
-----
This is a companion errata to https://www.rfc-editor.org/errata/eid5970 which identified the issue in Error-type 19 Error-value 1. The same issue exists for Error-type 20 Error-value 1 i.e. LSP Object is not part of the PCErr message.

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