Status of This Memo

This is an Internet Standards Track document.¶

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc9847.¶

Copyright Notice

Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1.Introduction

This document instructs IANA to make changes to a number of the IANAregistries related to Transport Layer Security (TLS) and DatagramTransport Layer Security (DTLS). These changes update the changes madein[RFC8447].¶

This specification adds a new value, "D" for discouraged, to the "Recommended"column of the selected TLS registries and adds a "Comment" column to allactive registries that do not already have a "Comment" column.¶

This specification also updates the registration request instructions.¶

2.Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and "OPTIONAL" in this document are to be interpreted asdescribed in BCP 14[RFC2119][RFC8174] when, and only when, theyappear in all capitals, as shown here.¶

3.Updating "Recommended" Column's Values

The instructions in this document update the "Recommended" column,originally added in[RFC8447] to add a third value, "D",indicating that a value is discouraged. The permitted valuesof the "Recommended" column are:¶

Y:

Indicates that the IETF has consensus that the item isRECOMMENDED. This only means that the associated mechanism is fit for the purpose for which it was defined. Careful reading of the documentation for the mechanism is necessary to understand the applicability of that mechanism. The IETF could recommend mechanisms that have limited applicability but will provide applicability statements that describe any limitations of the mechanism or necessary constraints on its use.¶

N:

Indicates that the item has not been evaluated by the IETF and that the IETF has made no statement about the suitability of the associated mechanism. This does not necessarily mean that the mechanism is flawed, only that no consensus exists. The IETF might have consensus to leave an item marked as "N" on the basis of the item having limited applicability or usage constraints.¶

D:

Indicates that the item is discouraged. This marking could be used to identify mechanisms that might result in problems if they are used, such as a weak cryptographic algorithm or a mechanism that might cause interoperability problems in deployment. When marking a registry entry as "D", either the "Reference" or the "Comment" columnMUST include sufficient information to determine why the marking has been applied. Implementers and usersSHOULD consult the linked references associated with the item to determine the conditions under which the itemSHOULD NOT orMUST NOT be used.¶

Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requiresIETF Standards Action with Expert Review or IESG Approval[RFC8126]. Not all items definedin Standards Track RFCs need to be setto "Y" or "D". Any item not otherwise specified is set to "N". The column isblank for values that are unassigned or reserved unless specifically set.¶

4.TLS ExtensionType Values Registry

In order to reflect the changes in the "Recommended" column allocation,IANA has updated the "TLS ExtensionType Values" registry as follows:¶

• Adjusted the registration procedure related to setting the "Recommended" column as follows:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Updated the "Recommended" column with the changes listed below. Entrieskeep their existing "Y" and "N" entries except for the entries in the following table.IANA has added a reference to this document for these entries.¶

• Updated the note on the "Recommended" column with text inSection 3.1.¶

• For the truncated_hmac, added the following link to the "Reference" column:https://www.iacr.org/archive/asiacrypt2011/70730368/70730368.pdf.¶

• For the two Reserved values above, added the following link in the "Reference" column:https://mailarchive.ietf.org/arch/msg/tls-reg-review/5BD62HBFjo_AsW-Y8ohVuWEe1gI/.¶

5.TLS Cipher Suites Registry

Several categories of cipher suites are discouraged for general use andare marked as "D".¶

Cipher suites that use NULL encryption do not provide the confidentialitynormally expected of TLS. Protocols and applications are often designedto require confidentiality as a security property. Thesecipher suitesMUST NOT be used in those cases.¶

Cipher suites marked as EXPORT use weak ciphers and were deprecated inTLS 1.1[RFC4346].¶

Cipher suites marked as anon do not provide any authentication, arevulnerable to on-path attacks, and were deprecated in TLS 1.1[RFC4346].¶

RC4 is a weak cipher and is deprecated in[RFC7465].¶

DES and the International Data Encryption Algorithm (IDEA) are not considered secure for general use and were deprecated in[RFC5469]. MD5 and SHA-1 are also not secure for general use and were deprecated in[RFC9155].¶

In order to reflect the changes in the "Recommended" column allocation,IANA has updated the "TLS Cipher Suites" registry as follows:¶

• Adjusted the registration procedure related to setting the "Recommended" column as follows:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Updated the "Recommended" column with the changes listed below. Entrieskeep their existing "Y" and "N" entries except for the entries in following table.IANA has added a reference to this document for these entries. This document does notmake any changes to the "DTLS-OK" column.¶

• Updated the note on the "Recommended" column with text inSection 3.1.¶

6.TLS Supported Groups Registry

In order to reflect the changes in the "Recommended" column allocation,IANA has updated the "TLS Supported Groups" registry as follows:¶

• Updated the registration policy to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Updated the "Recommended" column with the changes listed below. Entrieskeep their existing "Y" and "N" entries except for the entries in following table.IANA has added a reference to this document for these entries.¶

• Updated the note on the "Recommended" column with text inSection 3.1.¶

• Removed the "Elliptic curve groups" note from the registrationprocedures table.¶

• For each of the entries above, added the following link to the"Comment" column:https://datatracker.ietf.org/meeting/118/materials/slides-118-tls-rfc8447bis-00.¶

7.TLS Exporter Labels Registry

This document updates the registration procedure for the "TLS ExporterLabels" registry and updates the "Recommended" column allocation.IANA has updated the "TLS Exporter Labels" registry as follows:¶

• Changed the registration procedure from Specification Required toExpert Review and updated it to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Entries kept their existing "Recommended" column "Y" and "N" entries.¶

• Updated the note on the "Recommended" column with text inSection 3.1.¶

• Updated the note on the role of the expert reviewer as follows.¶

Note: The role of the designated expert is described inSection 17 of [RFC8447].Even though this registry does not require a specification, thedesignated expert[RFC8126] will strongly encourage registrantsto provide a link to a publicly available specification. AnInternet-Draft (that is posted and never published as an RFC)or a document from another standards body, industry consortium,university site, etc. is suitable for these purposes.The expert may provide more in-depth reviews, but their approvalshould not be taken as an endorsement of the exporter label. Theexpert also verifies that the label is a string consisting ofprintable ASCII characters beginning with "EXPORTER". IANAMUSTalso verify that one label is not a prefix of any other label.For example, labels "key" or "master secretary" are forbidden.¶

• Renamed the "Note" column to "Comment".¶

8.TLS Certificate Types Registry

In order to reflect the changes in the "Recommended" column allocation,IANA has updated the "TLS Certificate Types" registry as follows:¶

• Adjusted the registration procedure related to setting the "Recommended" column as follows:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Entries kept their existing "Recommended" column "Y" and "N" entries.¶

• Updated the note on the "Recommended" column with text inSection 3.1.¶

9.TLS HashAlgorithm Registry

TLS 1.0 and TLS 1.1 were deprecated[RFC8996]; TLS 1.2 willbe in use for some time. In order to reflect the changes in the "Recommended"column allocation, IANA has updated the "TLS HashAlgorithm" registryas follows:¶

• Updated the registration procedure to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Updated the "TLS HashAlgorithm" registry to add a "Recommended" columnas follows:¶

• Added a note on the "Recommended" column with text inSection 3.1.¶

10.TLS SignatureAlgorithm Registry

TLS 1.0 and TLS 1.1 were deprecated[RFC8996], TLS 1.2 willbe in use for some time. In order to reflect the changes in the "Recommended"column allocation, IANA has updated the "TLS SignatureAlgorithm" registryas follows:¶

• Updated the registration procedure to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Updated the "TLS SignatureAlgorithm" registry to add a "Recommended"column as follows:¶

• Added a note on the "Recommended" column with text inSection 3.1.¶

11.TLS ClientCertificateType Identifiers Registry

TLS 1.0 and TLS 1.1 were deprecated[RFC8996], TLS 1.2 willbe in use for some time. In order to reflect the changes in the "Recommended"column allocation, IANA has updated the "TLS ClientCertificateType Identifiers"registry as follows:¶

• Updated the registration procedure to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Updated the "TLS ClientCertificateType Identifiers" registry to add a "Recommended"column as follows:¶

• Added a note on the "Recommended" column with text inSection 3.1.¶

12.TLS PskKeyExchangeMode Registry

In order to reflect the changes in the "Recommended" column allocation,IANA has updated the "TLS PskKeyExchangeMode" registry as follows:¶

• Updated the registration procedure to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Entries kept their existing "Recommended" column "Y" and "N" entries.¶

• Updated note on the "Recommended" column with text inSection 3.1.¶

13.TLS SignatureScheme Registry

In order to reflect the changes in the "Recommended" column allocation,IANA has updated the "TLS SignatureScheme" registry as follows:¶

• Updated the registration procedure to include:¶

  Setting a value to "Y" or "D" or transitioning the value from "Y" or "D" in the "Recommended" column requires IETF Standards Action with Expert Review or IESG Approval[RFC8126].¶

• Added a reference to this document under the reference heading.¶

• Entries kept their existing "Recommended" column "Y" and "N" entries.¶

• Updated note on the "Recommended" column with text inSection 3.1.¶

14.Adding "Comment" Column

IANA has added a "Comment" column to the following registries:¶

• TLS ExtensionType Values¶

• TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs¶

• TLS CachedInformationType Values¶

• TLS Certificate Compression Algorithm IDs¶

• TLS ClientCertificateType Identifiers¶

• TLS Cipher Suites¶

• TLS ContentType¶

• TLS EC Point Formats¶

• TLS EC Curve Types¶

• TLS Supplemental Data Formats (SupplementalDataType)¶

• TLS UserMappingType Values¶

• TLS SignatureAlgorithm¶

• TLS HashAlgorithm¶

• TLS Authorization Data Formats¶

• TLS Heartbeat Message Types¶

• TLS Heartbeat Modes¶

• TLS SignatureScheme¶

• TLS PskKeyExchangeMode¶

• TLS KDF Identifiers¶

• TLS SSLKEYLOGFILE Labels¶

This list of registries is all registries that do not already have a"Comment" or "Note" column or that were not orphaned by TLS 1.3.¶

15.Expert Review of Current and Potential IETF and IRTF Documents

The intent of the Specification Required choice for TLS codepointsis to allow for easy registration for codepoints associated withprotocols and algorithms that are not being actively developed insidethe IETF or IRTF. When TLS-based technologies are being developed insidethe IETF or IRTF, they should be done in coordination with the TLS WG inorder to provide appropriate review. For this reason, unless the TLS WGChairs indicate otherwise via email, designatedexperts should decline codepoint registrations for documents thathave already been adopted or are being proposed for adoption by IETFworking groups or IRTF research groups.¶

16.Registration Requests

Registration requestsMUST be submitted in one of two ways:¶

1. By sending email to iana@iana.org; this emailSHOULDuse an appropriate subject (e.g., "Request to register value in TLSbar registry").¶

2. Using the online form athttps://www.iana.org/form/protocol-assignment.¶

Specification Required[RFC8126] registry requests are registered aftera three-week review period on the advice of one or more designatedexperts. However, to allow for the allocation of values prior topublication, the designated experts may approve registration once theyare satisfied that such a specification will be published.¶

17.Security Considerations

Recommended algorithms are regarded as secure for general use at thetime of registration; however, cryptographic algorithms and parameterswill be broken or weakened over time. It is possible that the"Recommended" status in the registry lags behind the most recent advancesin cryptanalysis. Implementers and users need to check that thecryptographic algorithms listed continue to provide the expected levelof security.¶

Designated experts ensure the specification is publicly available. They mayprovide more in-depth reviews. Their review should not be taken as anendorsement of the cipher suite, extension, supported group, etc.¶

18.IANA Considerations

This document is entirely about changes to TLS-related IANA registries.¶

19.Normative References

[RFC2119]

Bradner, S.,"Key words for use in RFCs to Indicate Requirement Levels",BCP 14,RFC 2119,DOI 10.17487/RFC2119,March 1997,<https://www.rfc-editor.org/info/rfc2119>.

[RFC4346]

Dierks, T. andE. Rescorla,"The Transport Layer Security (TLS) Protocol Version 1.1",RFC 4346,DOI 10.17487/RFC4346,April 2006,<https://www.rfc-editor.org/info/rfc4346>.

[RFC5469]

Eronen, P., Ed.,"DES and IDEA Cipher Suites for Transport Layer Security (TLS)",RFC 5469,DOI 10.17487/RFC5469,February 2009,<https://www.rfc-editor.org/info/rfc5469>.

[RFC7465]

Popov, A.,"Prohibiting RC4 Cipher Suites",RFC 7465,DOI 10.17487/RFC7465,February 2015,<https://www.rfc-editor.org/info/rfc7465>.

[RFC8126]

Cotton, M.,Leiba, B., andT. Narten,"Guidelines for Writing an IANA Considerations Section in RFCs",BCP 26,RFC 8126,DOI 10.17487/RFC8126,June 2017,<https://www.rfc-editor.org/info/rfc8126>.

[RFC8174]

Leiba, B.,"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words",BCP 14,RFC 8174,DOI 10.17487/RFC8174,May 2017,<https://www.rfc-editor.org/info/rfc8174>.

[RFC8447]

Salowey, J. andS. Turner,"IANA Registry Updates for TLS and DTLS",RFC 8447,DOI 10.17487/RFC8447,August 2018,<https://www.rfc-editor.org/info/rfc8447>.

[RFC8996]

Moriarty, K. andS. Farrell,"Deprecating TLS 1.0 and TLS 1.1",BCP 195,RFC 8996,DOI 10.17487/RFC8996,March 2021,<https://www.rfc-editor.org/info/rfc8996>.

[RFC9155]

Velvindron, L.,Moriarty, K., andA. Ghedini,"Deprecating MD5 and SHA-1 Signature Hashes in TLS 1.2 and DTLS 1.2",RFC 9155,DOI 10.17487/RFC9155,December 2021,<https://www.rfc-editor.org/info/rfc9155>.

Authors' Addresses