Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

Building Protocols with HTTP
RFC 9205 also known as BCP 56

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2023-12-12	(System)	Imported membership of rfc9205 in bcp56 via sync to the rfc-index
2023-12-12	(System)	No history of BCP56 is currently available in the datatracker before this point
2022-06-08	(System)	Received changes through RFC Editor sync (created alias RFC 9205, changed abstract to 'Applications often use HTTP as a substrate to create HTTP-based APIs. … Received changes through RFC Editor sync (created alias RFC 9205, changed abstract to '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.', changed pages to 27, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2022-06-08, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-httpbis-bcp56bis and RFC 3205)
2022-06-08	(System)	RFC published