Change:
2. <del> This document requests that IANA make changes to a number of DTLS- and TLS-related IANA registries. </del> <ins> 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. </ins> <del> In this document, we use the term "(D)TLS" to refer to registries that apply to both TLS and DTLS. Add "TLS" to registries' names for consistency amongst TLS-related registries. Change the IANA registry policy RFC5226 for the TLS ExtensionType Values, TLS Cipher Suite, and TLS ClientCertificateType Identifiers registries.  These changes register a small part of these code spaces for experimentation and private use. Add designated expert instructions as notes in the TLS ExtensionType Values, TLS Cipher Suite, TLS ClientCertificateType Identifiers, and TLS Exporter Label registries to inform users about what to expect from the designated expert. Add notes to indicate whether an extension, certain values of an extension, or an entire registry is only applicable pre-(D)TLS 1.3. Rename the NewSessionTicket TLS HandshakeType message registry entry RFC5077 to new_session_ticket to match the naming nomenclature for the other Handshake type names and to match with existing implementations. Rename the SessionTicket TLS extension to session_ticket to match the nomenclature for the other extensions' names. Add missing entry to the TLS Alert Registry for the no_application_protocol alert defined in RFC7301. Added "Recommended" column to TLS ExtensionType Values, TLS Cipher Suite, TLS Certificate Types, TLS Supported Groups, and TLS Exporters Label registries.  Initial values marked "Yes" are specified in IETF Standards Track documents; all others are marked "No".  This new column is intended to alter the incorrect perception that getting a code point somehow legitimizes the extension, cipher suite/algorithm, or exporter. Establish Designated Expert pool rules for Specification Required registries. </del> <ins> 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). </ins> This document proposes no changes to the registration policies for TLS Alert I-D.ietf-tls-tls13, TLS ContentType I-D.ietf-tls-tls13, TLS <del> HandshakeType, I-D.ietf-tls-tls13 and TLS Certificate Status Types RFC6961; the existing policies (Standards Action for the first three; IETF Review for the last), are appropriate for these one-byte code points because of their scarcity. </del> <ins> HandshakeType I-D.ietf-tls-tls13, and TLS Certificate Status Types RFC6961 registries; the existing policies (Standards Action for the first three; IETF Review for the last), are appropriate for these one-byte code points because of their scarcity. </ins> 3. <del> IANA is to update the names of the following registries to add "TLS" to for consistency with the other TLS-related extensions: </del> <ins> For consistency amongst TLS reqgistries, IANA [SHALL prepend/has prepended] "TLS" to the following registries: </ins> <del> Application-Layer Protocol Negotiation (ALPN) Protocol IDs, </del> <ins> Application-Layer Protocol Negotiation (ALPN) Protocol IDs RFC7301, </ins> ExtensionType Values, <del> Heartbeat Message Types, </del> <ins> Heartbeat Message Types RFC6520, and </ins> <del> Heartbeat Modes, and </del> <ins> Heartbeat Modes RFC6520. </ins> <del> Supported Groups. IANA is also to add a reference to this document for the registry whose names have been updated as a result of the above change.  The remainder of this document will use the registry names with the "TLS" prefix. </del> <ins> 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. </ins> 4. <del> Many of the TLS-related IANA registries were defined prior to RFC5226 where "IETF Consensus" was used instead of the RFC5226-defined "IETF Review".  To align with the new terminology, IANA is to update to use "IETF Review" in place of "IETF Consensus" in the following registries: </del> <ins> Many of the TLS-related IANA registries were defined prior to RFC8126 where "IETF Consensus" was used instead of the RFC8126-defined "IETF Review".  To align with the new terminology, IANA [SHALL update/has updated] the following registries to use "IETF Review" in place of "IETF Consensus": </ins> <del> TLS Authorization Data Formats </del> <ins> TLS Authorization Data Formats RFC4680} </ins> TLS Supplemental Data Formats (SupplementalDataType)

Discussion:
A pretty major rewrite to incorporate the rationale for changes into individual sections as opposed to having it at the beginning. Also fixing some formatting.