Draft: draft-ietf-tls-tls13

Commentary: RFC 5226 obsoleted RFC 2434 so we should refer to that to avoid a GENART review comment .
Paragraph (version A):
TLS Cipher Suite Registry: Values with the first byte in the range
0-254 (decimal) are assigned via Specification Required RFC2434.
Values with the first byte 255 (decimal) are reserved for Private
Use RFC2434.
Paragraph (version B):
TLS Cipher Suite Registry: Values with the first byte in the range
0-254 (decimal) are assigned via Specification Required RFC5226.
Values with the first byte 255 (decimal) are reserved for Private
Use RFC5226.
Paragraph (version A):
TLS ContentType Registry: Future values are allocated via
Standards Action RFC2434.
Paragraph (version A):
TLS Alert Registry: Future values are allocated via Standards
Action RFC2434.
Paragraph (version A):
TLS HandshakeType Registry: Future values are allocated via
Standards Action RFC2434.  IANA [SHALL update/has updated] this
registry to rename item 4 from "NewSessionTicket" to
"new_session_ticket".
Paragraph (version B):
TLS ContentType Registry: Future values are allocated via
Standards Action RFC5226.
Paragraph (version B):
TLS Alert Registry: Future values are allocated via Standards
Action RFC5226.
Paragraph (version B):
TLS HandshakeType Registry: Future values are allocated via
Standards Action RFC5226.  IANA [SHALL update/has updated] this
registry to rename item 4 from "NewSessionTicket" to
"new_session_ticket".
Paragraph (version A):
TLS ExtensionType Registry: Values with the first byte in the
range 0-254 (decimal) are assigned via Specification Required
RFC2434.  Values with the first byte 255 (decimal) are reserved
for Private Use RFC2434.  IANA [SHALL update/has updated] this
registry to include the "key_share", "pre_shared_key", and
"early_data" extensions as defined in this document.
Paragraph (version B):
TLS ExtensionType Registry: Values with the first byte in the
range 0-254 (decimal) are assigned via Specification Required
RFC5226.  Values with the first byte 255 (decimal) are reserved
for Private Use RFC5226.  IANA [SHALL update/has updated] this
registry to include the "key_share", "pre_shared_key", and
"early_data" extensions as defined in this document.
Paragraph (version A):
TLS SignatureScheme Registry: Values with the first byte in the
range 0-254 (decimal) are assigned via Specification Required
RFC2434.  Values with the first byte 255 (decimal) are reserved
for Private Use RFC2434.  Values with the first byte in the range
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
[shall be/ has been] initially populated with the values described
in signature-algorithms.  The following values SHALL be marked as
"Recommended": ecdsa_secp256r1_sha256, ecdsa_secp384r1_sha384,
rsa_pss_sha256, rsa_pss_sha384, rsa_pss_sha512, ed25519.
Paragraph (version B):
TLS SignatureScheme Registry: Values with the first byte in the
range 0-254 (decimal) are assigned via Specification Required
RFC5226.  Values with the first byte 255 (decimal) are reserved
for Private Use RFC5226.  Values with the first byte in the range
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
[shall be/ has been] initially populated with the values described
in signature-algorithms.  The following values SHALL be marked as
"Recommended": ecdsa_secp256r1_sha256, ecdsa_secp384r1_sha384,
rsa_pss_sha256, rsa_pss_sha384, rsa_pss_sha512, ed25519.