RFC Errata
RFC 8446, "The Transport Layer Security (TLS) Protocol Version 1.3", August 2018
Source of RFC: tls (sec)
Errata ID: 5682
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Richard Barnes
Date Reported: 2019-04-01
Section 4.3.2, B.3.2 says:
--- rfc8446.txt 2018-08-10 20:12:08.000000000 -0400 +++ rfc8446.erratum.txt 2019-04-01 15:44:54.000000000 -0400 @@ -3341,7 +3341,7 @@ struct { opaque certificate_request_context<0..2^8-1>; - Extension extensions<2..2^16-1>; + Extension extensions<0..2^16-1>; } CertificateRequest; @@ -7309,7 +7309,7 @@ struct { opaque certificate_request_context<0..2^8-1>; - Extension extensions<2..2^16-1>; + Extension extensions<0..2^16-1>; } CertificateRequest;
It should say:
--- rfc8446.txt 2018-08-10 20:12:08.000000000 -0400 +++ rfc8446.erratum.txt 2019-04-01 15:44:54.000000000 -0400 @@ -3341,7 +3341,7 @@ struct { opaque certificate_request_context<0..2^8-1>; - Extension extensions<2..2^16-1>; + Extension extensions<0..2^16-1>; } CertificateRequest; @@ -7309,7 +7309,7 @@ struct { opaque certificate_request_context<0..2^8-1>; - Extension extensions<2..2^16-1>; + Extension extensions<0..2^16-1>; } CertificateRequest;
Notes:
The length of this vector can never 2. It is either 0, if the vector is empty, or >=4, if the vector has at least one extension. Nothing elsewhere in the spec requires a non-zero number of extensions here, so this syntax should allow a zero-length vector.