Original text:
registries and their allocation policies are below: TLS Cipher Suite Registry: Values with the first byte in the range <del> 0-254 (decimal) are assigned via Specification Required RFC2434. </del>  Values with the first byte 255 (decimal) are reserved for Private <del> Use RFC2434. </del>  IANA [SHALL add/has added] the cipher suites listed in cipher- suites to the registry.  The "Value" and "Description" columns are D.sandj-tls-iana-registry-updates has been applied.]] TLS ContentType Registry: Future values are allocated via <del> Standards Action RFC2434. </del>  TLS Alert Registry: Future values are allocated via Standards <del> Action RFC2434. </del>  TLS HandshakeType Registry: Future values are allocated via <del> Standards Action RFC2434.  IANA [SHALL update/has updated] this </del>  registry to rename item 4 from "NewSessionTicket" to "new_session_ticket". TLS ExtensionType Registry: Values with the first byte in the range 0-254 (decimal) are assigned via Specification Required <del> RFC2434.  Values with the first byte 255 (decimal) are reserved for Private Use RFC2434.  IANA [SHALL update/has updated] this </del>  registry to include the "key_share", "pre_shared_key", and "early_data" extensions as defined in this document. TLS SignatureScheme Registry: Values with the first byte in the range 0-254 (decimal) are assigned via Specification Required <del> RFC2434.  Values with the first byte 255 (decimal) are reserved for Private Use RFC2434.  Values with the first byte in the range </del>  0-6 or with the second byte in the range 0-3 that are not currently allocated are reserved for backwards compatibility. This registry SHALL have a "Recommended" column.  The registry

Reviewer comments:
RFC 5226 obsoleted RFC 2434 so we should refer to that to avoid a GENART review comment.

Revised text:
registries and their allocation policies are below: TLS Cipher Suite Registry: Values with the first byte in the range  <ins> 0-254 (decimal) are assigned via Specification Required RFC5226. </ins> Values with the first byte 255 (decimal) are reserved for Private  <ins> Use RFC5226. </ins> IANA [SHALL add/has added] the cipher suites listed in cipher- suites to the registry.  The "Value" and "Description" columns are D.sandj-tls-iana-registry-updates has been applied.]] TLS ContentType Registry: Future values are allocated via  <ins> Standards Action RFC5226. </ins> TLS Alert Registry: Future values are allocated via Standards  <ins> Action RFC5226. </ins> TLS HandshakeType Registry: Future values are allocated via  <ins> Standards Action RFC5226.  IANA [SHALL update/has updated] this </ins> registry to rename item 4 from "NewSessionTicket" to "new_session_ticket". TLS ExtensionType Registry: Values with the first byte in the range 0-254 (decimal) are assigned via Specification Required  <ins> RFC5226.  Values with the first byte 255 (decimal) are reserved for Private Use RFC5226.  IANA [SHALL update/has updated] this </ins> registry to include the "key_share", "pre_shared_key", and "early_data" extensions as defined in this document. TLS SignatureScheme Registry: Values with the first byte in the range 0-254 (decimal) are assigned via Specification Required  <ins> RFC5226.  Values with the first byte 255 (decimal) are reserved for Private Use RFC5226.  Values with the first byte in the range </ins> 0-6 or with the second byte in the range 0-3 that are not currently allocated are reserved for backwards compatibility. This registry SHALL have a "Recommended" column.  The registry