RFC 9412: The ORIGIN Extension in HTTP/3
In plain English — editorial summary, not part of the RFC
The ORIGIN frame for HTTP/2 is equally applicable to HTTP/3, but it needs to be separately registered. This document describes the ORIGIN frame for HTTP/3.
Document record
- Document ID
- RFC9412
- Published
- June 2023
- Authors
- M. Bishop
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 5
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9406HyStart++: Modified Slow Start for TCPCurrent
May 2023
- RFC 9421HTTP Message SignaturesCurrent
February 2024
- RFC 9423Constrained RESTful Environments (CoRE) Target Attributes RegistryCurrent
April 2024
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 9435Considerations for Assigning a New Recommended Differentiated Services Code Point (DSCP)Current
July 2023
- RFC 9388Content Delivery Network Interconnection (CDNI) Footprint Types: Country Subdivision Code and Footprint UnionCurrent
July 2023
- RFC 9438CUBIC for Fast and Long-Distance NetworksCurrent
August 2023
- RFC 9440Client-Cert HTTP Header FieldCurrent
July 2023
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?