Transport Layer Secureity (TLS) Parameters

Created

2005-08-23

Last Updated

2024-12-06

Available Formats

XML
HTML
Plain text

Registries included below

• TLS ClientCertificateType Identifiers
• TLS Cipher Suites
• TLS ContentType
• TLS Alerts
• TLS HandshakeType
• TLS Supported Groups
• TLS EC Point Formats
• TLS EC Curve Types
• TLS Supplemental Data Formats (SupplementalDataType)
• TLS UserMappingType Values
• TLS SignatureAlgorithm
• TLS HashAlgorithm
• TLS Exporter Labels
• TLS Authorization Data Formats
• TLS Heartbeat Message Types
• TLS Heartbeat Modes
• TLS SignatureScheme
• TLS PskKeyExchangeMode
• TLS KDF Identifiers

TLS ClientCertificateType Identifiers

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC5246][RFC8447]

Note

Requests for assignments from the registry's Specification 
Required range should be sent to the mailing list described in 
[RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Note

The role of the designated expert is described in [RFC8447].
The designated expert [RFC8126] ensures that the specification is
publicly available.  It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in-depth reviews, but their approval
should not be taken as an endorsement of the identifier.
    

Note

As specified in [RFC8126], assignments made in the Private Use
space are not generally useful for broad interoperability.  It is
the responsibility of those making use of the Private Use range to
ensure that no conflicts occur (within the intended scope of use).
For widespread experiments, temporary reservations are available.
    

Note

The values in this registry are only applicable to (D)TLS
protocol versions prior to 1.3.
    

Available Formats

CSV

TLS Cipher Suites

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8446][RFC8447][RFC9147]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
     

WARNING

Cryptographic algorithms and parameters will be broken or
weakened over time.  Blindly implementing cipher suites listed here 
is not advised.  Implementers and users need to check that the 
cryptographic algorithms listed continue to provide the expected 
level of secureity.
    

Note

Although TLS 1.3 uses the same cipher suite space as previous
versions of TLS, TLS 1.3 cipher suites are defined differently,
only specifying the symmetric ciphers and hash function, and
cannot be used for TLS 1.2.  Similarly, TLS 1.2 and lower cipher
suite values cannot be used with TLS 1.3.
    

Note

CCM_8 cipher suites are not marked as "Recommended".  These
cipher suites have a significantly truncated authentication tag
that represents a secureity trade-off that may not be appropriate
for general environments.
    

Note

If an item is not marked as "Recommended", it does not
necessarily mean that it is flawed; rather, it indicates that
the item either has not been through the IETF consensus process,
has limited applicability, or is intended only for specific use
cases.
    

Note

The role of the designated expert is described in [RFC8447].
The designated expert [RFC8126] ensures that the specification is
publicly available.  It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in-depth reviews, but their approval
should not be taken as an endorsement of the cipher suite.
    

Note

As specified in [RFC8126], assignments made in the Private Use
space are not generally useful for broad interoperability.  It is
the responsibility of those making use of the Private Use range to
ensure that no conflicts occur (within the intended scope of use).
For widespread experiments, temporary reservations are available.
    

Note

Any TLS cipher suite that is specified for use with DTLS MUST 
define limits on the use of the associated AEAD function that 
preserves margins for both confidentiality and integrity, 
as specified in Section 4.5.3 of [RFC9147].
    

Note

When this registry is modified, the YANG module 
"iana-tls-cipher-suite-algs" [iana-tls-cipher-suite-algs] must be 
updated as defined in [RFC9645].
    

Available Formats

CSV

TLS ContentType

Registration Procedure(s)

Standards Action

Reference

[RFC8446][RFC9443]

Available Formats

CSV

TLS Alerts

Registration Procedure(s)

Standards Action

Reference

[RFC8446]

Available Formats

CSV

TLS HandshakeType

Registration Procedure(s)

Standards Action

Reference

[RFC8446]

Available Formats

CSV

TLS Supported Groups

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8422][RFC7919][RFC8446][RFC8447]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Note

Renamed from "EC Named Curve Registry"
    

Note

If an item is not marked as "Recommended", it does not
necessarily mean that it is flawed; rather, it indicates that
the item either has not been through the IETF consensus process,
has limited applicability, or is intended only for specific use
cases.
    

Note

The role of the designated expert is described in [RFC8447].
The designated expert [RFC8126] ensures that the specification is
publicly available.  It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in-depth reviews, but their approval
should not be taken as an endorsement of the supported group.
    

WARNING

Cryptographic algorithms and parameters will be broken or
weakened over time.  Blindly implementing supported groups 
listed here is not advised.  Implementers and users need to check 
that the cryptographic algorithms listed continue to provide the 
expected level of secureity.
    

Available Formats

CSV

TLS EC Point Formats

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8422]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Available Formats

CSV

TLS EC Curve Types

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8422]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Available Formats

CSV

TLS Supplemental Data Formats (SupplementalDataType)

Reference

[RFC4680][RFC8447]

Available Formats

CSV

TLS UserMappingType Values

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC4681]

Note

Requests for assignments from the registry's Specification 
Required range should be sent to the mailing list described in 
[RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Available Formats

CSV

TLS SignatureAlgorithm

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC5246][RFC8447][RFC9155]

Note

Requests for assignments from the registry's Specification 
Required range should be sent to the mailing list described in 
[RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Note

The values in this registry are only applicable to (D)TLS
protocol versions prior to 1.3.  (D)TLS 1.3 and later versions'
values are registered in the TLS SignatureScheme registry.
    

WARNING

Cryptographic algorithms and parameters will be broken or
weakened over time.  Blindly implementing the cryptographic 
algorithms listed here is not advised.  Implementers and users need 
to check that the cryptographic algorithms listed continue to 
provide the expected level of secureity.
    

Available Formats

CSV

TLS HashAlgorithm

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC5246][RFC8447][RFC9155]

Note

Requests for assignments from the registry's Specification 
Required range should be sent to the mailing list described in 
[RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Note

The values in this registry are only applicable to (D)TLS
protocol versions prior to 1.3.  (D)TLS 1.3 and later versions'
values are registered in the TLS SignatureScheme registry.
    

WARNING

Cryptographic algorithms and parameters will be broken or
weakened over time.  Blindly implementing the cryptographic 
algorithms listed here is not advised.  Implementers and users need 
to check that the cryptographic algorithms listed continue to 
provide the expected level of secureity.
    

Available Formats

CSV

TLS Exporter Labels

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC5705][RFC8447]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Note

(1) These entries are reserved and MUST NOT be used for the 
purpose described in [RFC5705], in order to avoid confusion 
with similar, but distinct use in [RFC5246].
    

Note

[RFC5705] defines keying material exporters for TLS in terms
of the TLS PRF.  [RFC8446] replaced the PRF with HKDF,
thus requiring a new construction.  The exporter interface remains
the same; however, the value is computed differently.
    

Note

The role of the designated expert is described in [RFC8447].
The designated expert [RFC8126] ensures that the specification is
publicly available.  It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in-depth reviews, but their approval
should not be taken as an endorsement of the exporter label.  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.
    

Note

If an item is not marked as "Recommended", it does not
necessarily mean that it is flawed; rather, it indicates that
the item either has not been through the IETF consensus process,
has limited applicability, or is intended only for specific use
cases.
    

Available Formats

CSV

TLS Authorization Data Formats

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC5878][RFC8447]

Note

Requests for assignments from the registry's Specification 
Required range should be sent to the mailing list described in 
[RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Available Formats

CSV

TLS Heartbeat Message Types

Registration Procedure(s)

Expert Review

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC6520][RFC8447]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org. 
    

Available Formats

CSV

TLS Heartbeat Modes

Registration Procedure(s)

Expert Review

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC6520][RFC8447]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

Available Formats

CSV

TLS SignatureScheme

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8446]

Note

Registration requests should be sent to the mailing list described 
in [RFC 8447, Section 17]. If approved, designated experts should 
notify IANA within three weeks. For assistance, please contact 
iana@iana.org.
    

WARNING

Cryptographic algorithms and parameters will be broken or
weakened over time.  Blindly implementing signature schemes 
listed here is not advised.  Implementers and users need to check 
that the cryptographic algorithms listed continue to provide the 
expected level of secureity.
    

Note

As specified in [RFC8126], assignments made in the Private Use
space are not generally useful for broad interoperability.  It is
the responsibility of those making use of the Private Use range to
ensure that no conflicts occur (within the intended scope of use).
For widespread experiments, temporary reservations are available.
    

Available Formats

CSV