Draft: draft-ietf-tls-iana-registry-updates

Commentary: Thank you 
 Thanks -- and a Happy New Year !
This document instructs IANA to make changes to a number of (D)TLS-
related IANA registries.  These changes were almost entirely
motiviated by the development of TLS1.3 I-D.ietf-tls-tls13.
The changes introduced by this document range from simple, e.g.,
adding notes, to commplex, e.g., changing a registry's registration
policy.  Intsead of listing the changes and their rationale in this,
the introducotry, section each section provides rationale for the
proposed change(s).
This document instructs IANA to make changes to a number of (D)TLS-
related IANA registries.  These changes were almost entirely
motivated by the development of TLS1.3 I-D.ietf-tls-tls13.
The changes introduced by this document range from simple, e.g.,
adding notes, to complex, e.g., changing a registry's registration
policy.  Instead of listing the changes and their rationale in this,
the introductory, section each section provides rationale for the
proposed change(s).
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 RFC2119 RFC8174 when, and only when, they appear in all capitals,
as shown here.
IANA [SHALL update/has updated] the reference for these four
registires to also refer to this document.  The remainder of this
document will use the registry names with the "TLS" prefix.
IANA [SHALL update/has updated] the reference for these four
registries to also refer to this document.  The remainder of this
document will use the registry names with the "TLS" prefix.
IANA [SHALL uppdate/has updated] the reference for this registry to
also refer to this document.
IANA [SHALL update/has updated] the reference for this registry to
also refer to this document.
ClientCertificateType Identifers marked as "Yes" are those
allocated via Standards Track RFCs.  ClientCertificateTypes marked
as "No" are not.
ClientCertificateType Identifiers marked as "Yes" are those
allocated via Standards Track RFCs.  ClientCertificateTypes marked
as "No" are not.
Experience has shown that the IETF Consensus registry policy for TLS
Certificate Types is too strict.  Based on WG consensus, the decision
was taken to change registration policy to Specification Required
RFC8126 while reserving a small part of the code space for
experimental and prviate use.  Therefore, IANA [SHALL add/has added]
a "Recommended" column to the registry.  X.509 and Raw Public Key are
"Yes".  All others are "No".  A Standards Track document RFC8126 is
required to register a certificate type with the value "Yes".  Future
Certificate Types MUST define the value of this column.  A Standards
Track document RFC8126 is required to register an entry with the
value "Yes".
Experience has shown that the IETF Consensus registry policy for TLS
Certificate Types is too strict.  Based on WG consensus, the decision
was taken to change registration policy to Specification Required
RFC8126 while reserving a small part of the code space for
experimental and private use.  Therefore, IANA [SHALL add/has added]
a "Recommended" column to the registry.  X.509 and Raw Public Key are
"Yes".  All others are "No".  A Standards Track document RFC8126 is
required to register a certificate type with the value "Yes".  Future
Certificate Types MUST define the value of this column.  A Standards
Track document RFC8126 is required to register an entry with the
value "Yes".
The following extensions are only applicable to (D)TLS protocol
vesions prior to 1.3: trusted_ca_keys, truncated_hmac,
ec_point_formats, srp, status_request_v2, encrypt_then_mac,
extended_master_secret, session_ticket, and renegotiation_info.
These extensions are not applicable to (D)TLS 1.3.
The following extensions are only applicable to (D)TLS protocol
versions prior to 1.3: trusted_ca_keys, truncated_hmac,
ec_point_formats, srp, status_request_v2, encrypt_then_mac,
extended_master_secret, session_ticket, and renegotiation_info.
These extensions are not applicable to (D)TLS 1.3.