[Pce] [Technical Errata Reported] RFC8231 (5376)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 02 June 2018 08:55 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 88B8E124239 for <pce@ietfa.amsl.com>; Sat, 2 Jun 2018 01:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 RdXToIJxXLiI for <pce@ietfa.amsl.com>; Sat, 2 Jun 2018 01:55:00 -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 C4B44124235 for <pce@ietf.org>; Sat, 2 Jun 2018 01:55:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9B768B8081E; Sat, 2 Jun 2018 01:54:36 -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, jonathan.hardwick@metaswitch.com, julien.meuric@orange.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: hkotni@juniper.net, pce@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180602085436.9B768B8081E@rfc-editor.org>
Date: Sat, 02 Jun 2018 01:54:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/qyj6LaNg9EP-ZCIBRuciwCWgads>
X-Mailman-Approved-At: Mon, 04 Jun 2018 02:55:26 -0700
Subject: [Pce] [Technical Errata Reported] RFC8231 (5376)
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: Sat, 02 Jun 2018 08:55:03 -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: http://www.rfc-editor.org/errata/eid5376 -------------------------------------- Type: Technical Reported by: Hari Krushna Kotni <hkotni@juniper.net> Section: 7.2 Original Text ------------- In case of SRP-ID-number wrapping, the last SRP-ID-number before the wrapping MUST be explicitly acknowledged, to avoid a situation where SRP-ID-numbers remain unacknowledged after the wrap. This means that the PCC may need to issue two PCUpd messages on detecting a wrap. Corrected Text -------------- In case of SRP-ID-number wrapping, the last SRP-ID-number before the wrapping MUST be explicitly acknowledged, to avoid a situation where SRP-ID-numbers remain unacknowledged after the wrap. This means that the PCC may need to issue two PCRpt messages on detecting a wrap. Notes ----- incase of srp id wrap, once PCC detects it, PCC needs to issue PCRpt message not PCUpd 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
- [Pce] [Technical Errata Reported] RFC8231 (5376) RFC Errata System