IANA Registry Updates for TLS and DTLS
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: The IESG <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Stephen Farrell <email@example.com>, firstname.lastname@example.org Subject: Protocol Action: 'IANA Registry Updates for Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)' to Proposed Standard (draft-ietf-tls-iana-registry-updates-05.txt) The IESG has approved the following document: - 'IANA Registry Updates for Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)' (draft-ietf-tls-iana-registry-updates-05.txt) as Proposed Standard This document is the product of the Transport Layer Security Working Group. The IESG contact persons are Benjamin Kaduk and Eric Rescorla. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-tls-iana-registry-updates/
Technical Summary This document is not very technical, it's about IANA registries: This document describes a number of changes to (D)TLS IANA registries that range from adding notes to the registry all the way to changing the registration policy. These changes were motivated by WG review of the (D)TLS-related registries undertaken as part of the TLS1.3 development process. This document updates many (D)TLS RFCs 3749, 5077, 4680, 5246, 5705, 5878, 6520, and 7301. Working Group Summary This draft has been discussed at multiple IETFs most recently at IETF100: https://datatracker.ietf.org/meeting/100/materials/slides-100-tls-sessa-iana-registry-updates/ There's not been a lot of review because most people consider this administrivia that others should do; most just want the rules relaxed. A couple of notable reviews have been provided as noted below. The most important change - to loosen registrations while at the same time adding a "recommended" column to key registries requiring standards action for a "yes" value, had clear WG consensus. Various other WG documents depend on these changes being made and more will in the near future. Document Quality This document is essentially administrative, so the important considerations are to ensure consistency amongst it, the TLS 1.3 spec, and the existing registry contents, as well as internal consistency about the handling for various attributes, such as the "Recommended" column, warning notes to be added to registries, and review policies. Martin Thomson and Eric Rescorla have reviewed previous versions of the document. Personnel Stephen Farrell is the Document Shepherd. Benjamin Kaduk is the Responsible Area Director. The IANA Expert(s) for the registries in this document are: Yoav Nir <email@example.com>, Rich Salz <firstname.lastname@example.org>, and Nick Sullivan <email@example.com> . The named experts have been approved previously on the March 8, 2018 Formal telechat.
RFC Editor Note Section 15 mentions "values with the first byte in the range" (twice), but there is only a single byte, so these should just be "values in the range". Please also note that the traditional "IANA shall do/has done" constructions to be resolved to the past tense appear throughout the document, not just in an IANA considerations section.