Original text:
Add the following: <del> Note: The designated expert RFC5226 only ensures that the specification is publicly available. </del>  10. IANA is to add the following note to the TLS Exporter Label Registry:  IANA is to also to add a "Recommended" column to the TLS Exporter Label registry.  The table that follows has been generated by marking Standards Track RFCs as "Yes" and all others as "No".  Future IANA is also to add the following note:  12. IANA is to add the following entry to the TLS Alert Registry (the IANA is to add the following to the TLS ExtensionType Values registry:  15. To make it clear that (D)TLS 1.3 has orphaned certain registries Add the following to the TLS Compression Method Identifiers registry RFC3749: <del> Note: Value 0 (NULL) is the only value in this registry applicable to (D)TLS protocol version 1.3 or later. </del>  Add the following to the TLS HashAlgorithm RFC5246 and TLS SignatureAlgorithm registries RFC5246: <del> Note: The values in this registry are only applicable to (D)TLS protocol versions prior to 1.3. </del>  Update the "References" in the TLS Compression Method Identifiers, TLS HashAlgorithm RFC5246 and TLS SignatureAlgorithm registries to

Reviewer comments:
I'm fairly sure that I sent these in already. Was there a regression? The current build has lines that are insanely long. This corrects that (and removes a warning caused by an open bracket).
I thought I fixed it, but I guess I'd missed it. I've got a fairly long rewrite that I hope to land early next that I think also addresses these.
Hoping that this is fixed via , which is pretty big set of editorial changes.

Revised text:
Add the following:  <ins> The designated expert RFC5226 only ensures that the specification is publicly available. </ins> 10. IANA is to add the following note to the TLS Exporter Label Registry: <ins> RFC5705 defines keying material exporters for TLS in terms of the TLS PRF.  I-D.ietf-tls-tls13 replaced the PRF with HKDF, thus requiring a new construction.  The exporter interface remains the same, however the value is computed different. </ins> IANA is to also to add a "Recommended" column to the TLS Exporter Label registry.  The table that follows has been generated by marking Standards Track RFCs as "Yes" and all others as "No".  Future IANA is also to add the following note: <ins> The designated expert RFC5226 ensures that the specification is publicly available.  The expert also verifies that the label is a string consisting of printable ASCII characters beginning with "EXPORTER".  IANA MUST also verify that one label is not a prefix of any other label.  For example, labels "key" or "master secretary" are forbidden. </ins> 12. IANA is to add the following entry to the TLS Alert Registry (the IANA is to add the following to the TLS ExtensionType Values registry: <ins> 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 are not applicable to DTLS 1.3. </ins> 15. To make it clear that (D)TLS 1.3 has orphaned certain registries Add the following to the TLS Compression Method Identifiers registry RFC3749:  <ins> Value 0 (NULL) is the only value in this registry applicable to (D)TLS protocol version 1.3 or later. </ins> Add the following to the TLS HashAlgorithm RFC5246 and TLS SignatureAlgorithm registries RFC5246:  <ins> The values in this registry are only applicable to (D)TLS protocol versions prior to 1.3. </ins> Update the "References" in the TLS Compression Method Identifiers, TLS HashAlgorithm RFC5246 and TLS SignatureAlgorithm registries to