[TLS] [Editorial Errata Reported] RFC9257 (7643)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 17 September 2023 13:22 UTC

To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: hvn@radiatorsoftware.com, housley@vigilsec.com, jonathan.hoyland@gmail.com, mohit@iki.fi, caw@heapingbits.net, tls@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230917132239.AD7287FDC1@rfcpa.amsl.com>
Date: Sun, 17 Sep 2023 06:22:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/AcdjmOL8Brt7BNB_kPAzODhxMns>
Subject: [TLS] [Editorial Errata Reported] RFC9257 (7643)
Precedence: list

The following errata report has been submitted for RFC9257,
"Guidance for External Pre-Shared Key (PSK) Usage in TLS".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7643

--------------------------------------
Type: Editorial
Reported by: Heikki Vatiainen <hvn@radiatorsoftware.com>

Section: 6.1. Stack Interface

Original Text
-------------
* OpenSSL and BoringSSL: Applications can specify support for
external PSKs via distinct ciphersuites in TLS 1.2 and below.
Also, they can then configure callbacks that are invoked for PSK
selection during the handshake. These callbacks must provide a
PSK identity and key. The exact format of the callback depends on
the negotiated TLS protocol version, with new callback functions
added specifically to OpenSSL for TLS 1.3 [RFC8446] PSK support.
The PSK length is validated to be between 1-256 bytes (inclusive).
The PSK identity may be up to 128 bytes long.

Corrected Text
--------------
* OpenSSL and BoringSSL: Applications can specify support for
external PSKs via distinct ciphersuites in TLS 1.2 and below.
Also, they can then configure callbacks that are invoked for PSK
selection during the handshake. These callbacks must provide a
PSK identity and key. The exact format of the callback depends on
the negotiated TLS protocol version, with new callback functions
added specifically to OpenSSL for TLS 1.3 [RFC8446] PSK support.
The PSK length is validated to be between 1-256 bytes (inclusive).
The PSK identity may be up to 128 bytes long. OpenSSL 3.0
increased PSK maximum length to 512 bytes and PSK identity maximum
length to 256 bytes to match existing implementations and
specifications.

Notes
-----
OpenSSL PSK length and PSK identity length were increased to 256 and 512 octets, respectively, for OpenSSL 3.0. There appear to be implementations and specifications that require these longer lengths. See here for more information:
https://github.com/openssl/openssl/pull/12777
https://github.com/openssl/openssl/pull/12771

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.

--------------------------------------
RFC9257 (draft-ietf-tls-external-psk-guidance-06)
--------------------------------------
Title : Guidance for External Pre-Shared Key (PSK) Usage in TLS
Publication Date : July 2022
Author(s) : R. Housley, J. Hoyland, M. Sethi, C. A. Wood
Category : INFORMATIONAL
Source : Transport Layer Security
Area : Security
Stream : IETF
Verifying Party : IESG

[TLS] [Editorial Errata Reported] RFC9257 (7643) RFC Errata System
Re: [TLS] [Editorial Errata Reported] RFC9257 (76… Chris Smiley
Re: [TLS] [Editorial Errata Reported] RFC9257 (76… Salz, Rich