RFC 8740: Using TLS 1.3 with HTTP/2
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9113.
Current document in this lineage: RFC 9113 — HTTP/2
In plain English — editorial summary, not part of the RFC
This document updates RFC 7540 by forbidding TLS 1.3 post-handshake authentication, as an analog to the existing TLS 1.2 renegotiation restriction.
Document record
- Document ID
- RFC8740
- Published
- February 2020
- Authors
- D. Benjamin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 5
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 7540 (2015)
- RFC 8740 (2020)
- RFC 9113 (2022) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9111HTTP CachingCurrent
June 2022
- RFC 9112HTTP/1.1Updated
June 2022
- RFC 8336The ORIGIN HTTP/2 FrameCurrent
March 2018
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
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?