[Emu] [Technical Errata Reported] RFC9190 (7577)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 29 July 2023 23:07 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1DBC151542 for <emu@ietfa.amsl.com>; Sat, 29 Jul 2023 16:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.865
X-Spam-Level:
X-Spam-Status: No, score=-0.865 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXsOZz0CGHmr for <emu@ietfa.amsl.com>; Sat, 29 Jul 2023 16:07:55 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7001AC15153F for <emu@ietf.org>; Sat, 29 Jul 2023 16:07:55 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 4EA614C94A; Sat, 29 Jul 2023 16:07:55 -0700 (PDT)
To: john.mattsson@ericsson.com, mohit@iki.fi, rdd@cert.org, paul.wouters@aiven.io, joe@salowey.net, peter@akayla.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aland@freeradius.org, emu@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230729230755.4EA614C94A@rfcpa.amsl.com>
Date: Sat, 29 Jul 2023 16:07:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/P8gUkxMI1o1AT1_neYPqW6so3Rs>
Subject: [Emu] [Technical Errata Reported] RFC9190 (7577)
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jul 2023 23:07:59 -0000
The following errata report has been submitted for RFC9190, "EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7577 -------------------------------------- Type: Technical Reported by: Alan DeKok <aland@freeradius.org> Section: 2.5 Original Text ------------- When an EAP-TLS server has successfully processed the TLS client Finished and sent its last handshake message (Finished or a post- handshake message), it sends an encrypted TLS record with application data 0x00. The encrypted TLS record with application data 0x00 is a protected success result indication, as defined in [RFC3748] ... Corrected Text -------------- (append) If the EAP-TLS peer does not see the protected success indication, it MUST behave as if it had received an EAP Failure instead. Notes ----- This is largely a nit, but it's reasonable to say this. The existing text discussed what the server must do, But it does not say what the peer does if the server fails to behave this way, 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. -------------------------------------- RFC9190 (draft-ietf-emu-eap-tls13-21) -------------------------------------- Title : EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3 Publication Date : February 2022 Author(s) : J. Preuß Mattsson, M. Sethi Category : PROPOSED STANDARD Source : EAP Method Update Area : Security Stream : IETF Verifying Party : IESG
- [Emu] [Technical Errata Reported] RFC9190 (7577) RFC Errata System
- Re: [Emu] [Technical Errata Reported] RFC9190 (75… Alan DeKok