RFC 9205: Building Protocols with HTTP
In plain English — editorial summary, not part of the RFC
Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet but might be applicable in other situations. This document obsoletes RFC 3205.
Document record
- Document ID
- RFC9205
- Published
- June 2022
- Authors
- M. Nottingham
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- wit
- Pages
- 27
- Also known as
- BCP56
- Obsoletes:
- RFC 3205
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9204QPACK: Field Compression for HTTP/3Current
June 2022
- RFC 9209The Proxy-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
- RFC 9213Targeted HTTP Cache ControlCurrent
June 2022
- RFC 9193Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-FormatCurrent
June 2022
- RFC 9218Extensible Prioritization Scheme for HTTPCurrent
June 2022
- RFC 9220Bootstrapping WebSockets with HTTP/3Current
June 2022
- RFC 9221An Unreliable Datagram Extension to QUICCurrent
March 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?