metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2

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

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 specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK]

Document record

Document ID
RFC5246
Published
August 2008
Authors
T. Dierks; E. Rescorla
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
104
Also known as
—
Obsoletes:
RFC 3268, RFC 4346, RFC 4366
Obsoleted by:
RFC 8446, RFC 9846
Updates:
RFC 4492
Updated by:
RFC 5746, RFC 5878, RFC 6176, RFC 7465, RFC 7507, RFC 7568, RFC 7627, RFC 7685, RFC 7905, RFC 7919, RFC 8447, RFC 9155, RFC 10015

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

15 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/5246-the-transport-layer-security-tls-protocol-version-1-2