[Pce] [Errata Held for Document Update] RFC8253 (5180)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 12 December 2017 21:32 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 5D9E3128A32; Tue, 12 Dec 2017 13:32:54 -0800 (PST)
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 ZR99_jThnFJ2; Tue, 12 Dec 2017 13:32:52 -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 D148A127444; Tue, 12 Dec 2017 13:32:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D27B9B80A8E; Tue, 12 Dec 2017 13:32:27 -0800 (PST)
To: housley@vigilsec.com, diego.r.lopez@telefonica.com, oscar.gonzalezdedios@telefonica.com, sunseawq@huawei.com, dhruv.ietf@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: db3546@att.com, iesg@ietf.org, pce@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20171212213227.D27B9B80A8E@rfc-editor.org>
Date: Tue, 12 Dec 2017 13:32:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/xYrq4z86V846LVHkF0C0PvTdBOg>
Subject: [Pce] [Errata Held for Document Update] 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: Tue, 12 Dec 2017 21:32:54 -0000
The following errata report has been held for document update 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 -------------------------------------- Status: Held for Document Update Type: Editorial Reported by: Russ Housley <housley@vigilsec.com> Date Reported: 2017-11-06 Held by: Deborah Brungard (IESG) 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. -------------------------------------- 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] [Errata Held for Document Update] RFC8253 (… RFC Errata System