The Transport Layer Security (TLS) Protocol Version 1.3
This specification has been revised 14 times since RFC 2246 (1999). Each document below formally obsoleted the one before it; the versions still in force are listed first.
Revision timeline
Current versions — implement against these
Superseded versions — historical reference only
- RFC 2246The TLS Protocol Version 1.0ObsoletedJanuary 1999historicreplaced by RFC4346
- RFC 3268Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)ObsoletedJuly 2002proposed standardreplaced by RFC5246
- RFC 3546Transport Layer Security (TLS) ExtensionsObsoletedJune 2003proposed standardreplaced by RFC4366
- RFC 4346The Transport Layer Security (TLS) Protocol Version 1.1ObsoletedApril 2006historicreplaced by RFC5246
- RFC 4366Transport Layer Security (TLS) ExtensionsObsoletedApril 2006proposed standardreplaced by RFC5246, RFC6066
- RFC 4492Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)ObsoletedMay 2006informationalreplaced by RFC8422
- RFC 4507Transport Layer Security (TLS) Session Resumption without Server-Side StateObsoletedMay 2006proposed standardreplaced by RFC5077
- RFC 5077Transport Layer Security (TLS) Session Resumption without Server-Side StateObsoletedJanuary 2008proposed standardreplaced by RFC8446, RFC9846
- RFC 5246The Transport Layer Security (TLS) Protocol Version 1.2ObsoletedAugust 2008proposed standardreplaced by RFC8446, RFC9846
- RFC 6961The Transport Layer Security (TLS) Multiple Certificate Status Request ExtensionObsoletedJune 2013proposed standardreplaced by RFC8446, RFC9846
- RFC 7627Transport Layer Security (TLS) Session Hash and Extended Master Secret ExtensionObsoletedSeptember 2015proposed standardreplaced by RFC9846
- RFC 8422Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) Versions 1.2 and EarlierObsoletedAugust 2018proposed standardreplaced by RFC9846
- RFC 8446The Transport Layer Security (TLS) Protocol Version 1.3ObsoletedAugust 2018proposed standardreplaced by RFC9846
This lineage is derived automatically from the “obsoletes” relationships recorded in the public RFC Editor index — no editorial judgement is applied to the ordering. The most recent document in the chain is RFC 9846 (July 2026).