Transport Layer Security (TLS) Extensions

Created

2005-11-15

Last Updated

2024-10-22

Available Formats

XML
HTML
Plain text

Registries included below

• TLS ExtensionType Values
• TLS Certificate Types
• TLS Certificate Status Types
• TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs
• TLS CachedInformationType Values
• TLS Certificate Compression Algorithm IDs

TLS ExtensionType Values

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8446][RFC8447][RFC9146]

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

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 extension.  
    

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

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 addition of the "CR" to the "TLS 1.3" column for the
server_name(0) extension only marks the extension as valid in a 
ClientCertificateRequest created as part of client-generated
authenticator requests.
    

Available Formats

CSV

TLS Certificate Types

Registration Procedure(s)

Specification Required

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC6091][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

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 certificate type.
    

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 Certificate Status Types

Registration Procedure(s)

IETF Review

Reference

[RFC6961][RFC8446]

Available Formats

CSV

TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs

Registration Procedure(s)

Expert Review

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC7301][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 CachedInformationType Values

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC7924]

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 Certificate Compression Algorithm IDs

Expert(s)

Yoav Nir, Rich Salz, Nick Sullivan

Reference

[RFC8879]

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

Footnotes

This entry reserves an identifier for use within a cleartext version 
of a protocol and is not allowed to appear in a TLS ALPN negotiation.
    

Only appears in inner CH.