RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1
In plain English — editorial summary, not part of the RFC
In HTTP/1.1, the client can request a change to a new protocol on the existing connection. This document discusses the security considerations that apply to data sent by the client before this request is confirmed and adds new requirements to RFCs 9112 and 9298 to avoid related security issues.
Document record
- Document ID
- RFC9931
- Published
- March 2026
- Authors
- B. Schwartz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7639The ALPN HTTP Header FieldCurrent
August 2015
- RFC 9937Proportional Rate Reduction (PRR)Current
December 2025
- RFC 9952Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLSCurrent
March 2026
- RFC 9953DNS over CoAP (DoC)Current
March 2026
- RFC 9956A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated ServicesCurrent
May 2026
- RFC 9959Careful Resume: Convergence of Congestion Control from Retained StateCurrent
May 2026
- RFC 9897Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple AddressesCurrent
January 2026
- RFC 9876Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-FormatsCurrent
November 2025
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?