metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4366: Transport Layer Security (TLS) Extensions

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5246, RFC 6066.

Current document in this lineage: RFC 6066 — Transport Layer Security (TLS) Extensions: Extension Definitions; RFC 9846 — The Transport Layer Security (TLS) Protocol Version 1.3

In plain English — editorial summary, not part of the RFC

This document describes extensions that may be used to add functionality to Transport Layer Security (TLS). It provides both generic extension mechanisms for the TLS handshake client and server hellos, and specific extensions using these generic mechanisms. The extensions may be used by TLS clients and servers. The extensions are backwards compatible: communication is possible between TLS clients that support the extensions and TLS servers that do not support the extensions, and vice versa. [STANDARDS-TRACK]

Document record

Document ID
RFC4366
Published
April 2006
Authors
S. Blake-Wilson; M. Nystrom; D. Hopwood; J. Mikkelsen; T. Wright
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
30
Also known as
—
Obsoletes:
RFC 3546
Obsoleted by:
RFC 5246, RFC 6066
Updates:
RFC 4346
Updated by:
RFC 5746

Topics

Standards lineage

This document is one revision in a chain of 15 RFCs, each formally replacing the one before it.

  1. RFC 2246 (1999)
  2. RFC 3268 (2002)
  3. RFC 3546 (2003)
  4. RFC 4346 (2006)
  5. RFC 4366 (2006)
  6. RFC 4492 (2006)
  7. RFC 4507 (2006)
  8. RFC 5077 (2008)
  9. RFC 5246 (2008)
  10. RFC 6066 (2011)
  11. RFC 6961 (2013)
  12. RFC 7627 (2015)
  13. RFC 8422 (2018)
  14. RFC 8446 (2018)
  15. RFC 9846 (2026) ✓

Read the full history of The Transport Layer Security (TLS) Protocol Version 1.3 →

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4366-transport-layer-security-tls-extensions