The following errata report has been verified for RFC8446,
"The Transport Layer Security (TLS) Protocol Version 1.3". 

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

--------------------------------------
Status: Verified
Type: Technical

Reported by: Nizar Nadif <[email protected]>
Date Reported: 2025-05-19
Verified by: Deb Cooley (IESG)

Section: 4.1.2

Original Text
-------------
 struct {
        ProtocolVersion legacy_version = 0x0303;        /* TLS v1.2 */
        Random random;
        opaque legacy_session_id<0..32>;
        CipherSuite cipher_suites<2..2^16-2>;
        opaque legacy_compression_methods<1..2^8-1>;
        Extension extensions<8..2^16-1>;
 } ClientHello;

Corrected Text
--------------
struct {
        ProtocolVersion legacy_version = 0x0303;        /* TLS v1.2 */
        Random random;
        opaque legacy_session_id<0..32>;
        CipherSuite cipher_suites<2..2^16-2>;
        opaque legacy_compression_methods<1..2^8-1>;
        Extension extensions<7..2^16-1>;
} ClientHello;

Notes
-----
The minimum size of the ClientHello’s extensions is 7 as the bytes of the 
SupportedVersions field are at least:
- 2 bytes for the type of extension;
- 2 bytes for the length of the extension;
- 1 byte for the length of the following versions;
- 2 bytes per version (and there is at least 1 version).

The typo is also present in the section B.3.1.

This has been fixed in 8446bis here:  
https://github.com/tlswg/tls13-spec/pull/1420

--------------------------------------
RFC8446 (draft-ietf-tls-tls13-28)
--------------------------------------
Title               : The Transport Layer Security (TLS) Protocol Version 1.3
Publication Date    : August 2018
Author(s)           : E. Rescorla
Category            : PROPOSED STANDARD
Source              : Transport Layer Security
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
TLS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to