[Pce] [Editorial Errata Reported] RFC8253 (5180)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 06 November 2017 21:46 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 7D7E013FC81 for <pce@ietfa.amsl.com>; Mon, 6 Nov 2017 13:46:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 EYKDQNx8qaNU for <pce@ietfa.amsl.com>; Mon, 6 Nov 2017 13:46:43 -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 2C22613FC7E for <pce@ietf.org>; Mon, 6 Nov 2017 13:46:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CEE79B80D7C; Mon, 6 Nov 2017 13:46:29 -0800 (PST)
To: diego.r.lopez@telefonica.com, oscar.gonzalezdedios@telefonica.com, sunseawq@huawei.com, dhruv.ietf@gmail.com, akatlas@gmail.com, db3546@att.com, aretana.ietf@gmail.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: housley@vigilsec.com, pce@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20171106214629.CEE79B80D7C@rfc-editor.org>
Date: Mon, 06 Nov 2017 13:46:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/K-pva1sd-NmTB-p23WUKPC50xsc>
X-Mailman-Approved-At: Tue, 07 Nov 2017 00:09:01 -0800
Subject: [Pce] [Editorial Errata Reported] RFC8253 (5180)
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: Mon, 06 Nov 2017 21:46:44 -0000
The following errata report has been submitted for RFC8253, "PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5180 -------------------------------------- Type: Editorial Reported by: Russ Housley <housley@vigilsec.com> Section: 3.4 Original Text ------------- * PCEPS implementations MUST, at a minimum, support negotiation of the TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 [RFC6460] and SHOULD support TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as well. ... Corrected Text -------------- * PCEPS implementations MUST, at a minimum, support negotiation of the TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 [RFC5289] and SHOULD support TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as well. ... Notes ----- RFC 6460 makes reference to the TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ciphersuites, but it does not define them. These ciphersuites are defined in RFC 5289. 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. -------------------------------------- RFC8253 (draft-ietf-pce-pceps-18) -------------------------------------- Title : PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP) Publication Date : October 2017 Author(s) : D. Lopez, O. Gonzalez de Dios, Q. Wu, D. Dhody Category : PROPOSED STANDARD Source : Path Computation Element Area : Routing Stream : IETF Verifying Party : IESG
- [Pce] [Editorial Errata Reported] RFC8253 (5180) RFC Errata System