Draft: draft-ietf-tls-rfc8447bis

Commentary: PTAL .
This document obsoletes RFC8447 and updates the following RFCs: 3749,
5077, 4680, 5246, 5705, 5878, 6520, 7301.
This document obsoletes RFC 8447 and updates the following RFCs:
3749, 5077, 4680, 5246, 5705, 5878, 6520, and 7301.
This document updates RFC8447 the values of "Recommended" column.
This document refers to I-D.ietf-tls-rfc8446bis instead of RFC8446.
This document obsoletes RFC8447 and revises the values of
"Recommended" column.  It also updates references to RFC8446 with I-
D.ietf-tls-rfc8446bis and RFC8447 with I-D.ietf-tls-rfc8447bis.
Values with the first byte in the range 0-254 (decimal) are
assigned via Specification Required RFC8126.  Values with the
first byte 255 (decimal) are reserved for Private Use RFC8126.
The extensions added by RFC8446 are omitted from the above table;
additionally, token_binding is omitted, since I-D.ietf-tokbind-
negotiation specifies the value of the "Recommended" column as for
this extension.
RFC8446 also uses the TLS ExtensionType Values registry originally
created in RFC4366.  The following text is from RFC8446 and is
included here to ensure alignment between these specifications.
IANA [SHALL update/has updated] this registry to include the
"key_share", "pre_shared_key", "psk_key_exchange_modes",
"early_data", "cookie", "supported_versions",
"certificate_authorities", "oid_filters", "post_handshake_auth",
and "signature_algorithms_cert", extensions with the values
defined in RFC8446 and the "Recommended" value of "Y".
IANA [SHALL update/has updated] this registry to include a "TLS
1.3" column that lists the messages in which the extension may
appear.  This column [SHALL be/has been] initially populated from
the table in Section 4.2 of RFC8446 with any extension not listed
there marked as "-" to indicate that it is not used by TLS 1.3.
The designated expert RFC8126 ensures that the specification is
publicly available.  It is sufficient to have an Internet-Draft (that
is posted and never published as an RFC) or a document from another
standards body, industry consortium, university site, etc.  The
expert may provide more in-depth reviews, but their approval should
not be taken as an endorsement of the extension.
The extensions added by I-D.ietf-tls-rfc8446bis are omitted from the
above table; additionally, token_binding is omitted, since RFC8472
specifies the value of the "Recommended" column as for this
extension.
I-D.ietf-tls-rfc8446bis also uses the TLS ExtensionType Values
registry originally created in RFC4366.  The following text is from
I-D.ietf-tls-rfc8446bis and is included here to ensure alignment
between these specifications.
IANA [SHALL update/has updated] this registry to include the
"key_share", "pre_shared_key", "psk_key_exchange_modes",
"early_data", "cookie", "supported_versions",
"certificate_authorities", "oid_filters", "post_handshake_auth",
and "signature_algorithms_cert", extensions with the values
defined in I-D.ietf-tls-rfc8446bis and the "Recommended" value of
"Y".
IANA [SHALL update/has updated] this registry to include a "TLS
1.3" column that lists the messages in which the extension may
appear.  This column [SHALL be/has been] initially populated from
the table in Section 4.2 of I-D.ietf-tls-rfc8446bis with any
extension not listed there marked as "-" to indicate that it is
not used by TLS 1.3.
The TLS 1.3 cipher suites specified by RFC8446 are not listed here;
that document provides for their "Recommended" status.
The TLS 1.3 cipher suites specified by I-D.ietf-tls-rfc8446bis are
not listed here; that document provides for their "Recommended"
status.
Similar to cipher suites, supported groups have proliferated over
time, and some use the registry to measure implementations.
Therefore, IANA [SHALL add/has added] a "Recommended" column with a
"Y" for secp256r1, secp384r1, x25519, and x448, while all others are
"N".  These "Y" groups are taken from Standards Track RFCs; RFC8422
elevates secp256r1 and secp384r1 to Standards Track.  Not all groups
from RFC8422, which is Standards Track, are marked as "Y"; these
groups apply to TLS 1.3 RFC8446 and previous versions of TLS.  The
"Recommended" column is assigned a value of "N" unless explicitly
requested, and adding a value with a "Recommended" value of "Y"
requires Standards Action RFC8126.  IESG Approval is REQUIRED for a
Y->N transition.
Similar to cipher suites, supported groups have proliferated over
time, and some use the registry to measure implementations.
Therefore, IANA [SHALL add/has added] a "Recommended" column with a
"Y" for secp256r1, secp384r1, x25519, and x448, while all others are
"N".  These "Y" groups are taken from Standards Track RFCs; RFC8422
elevates secp256r1 and secp384r1 to Standards Track.  Not all groups
from RFC8422, which is Standards Track, are marked as "Y"; these
groups apply to TLS 1.3 I-D.ietf-tls-rfc8446bis and previous versions
of TLS.  The "Recommended" column is assigned a value of "N" unless
explicitly requested, and adding a value with a "Recommended" value
of "Y" requires Standards Action RFC8126.  IESG Approval is REQUIRED
for a Y->N transition.
Values in the range 0-223 (decimal) are assigned via Specification
Required RFC8126.  Values in the range 224-255 (decimal) are
reserved for Private Use RFC8126.