draft-ietf-httpbis-binary-message-00.txt		draft-ietf-httpbis-binary-message-latest.txt
	HTTP Working Group M. Thomson		HTTP Working Group M. Thomson
	Internet-Draft Mozilla		Internet-Draft Mozilla
	Intended status: Standards Track C. Wood		Intended status: Standards Track C. Wood
	Expires: May 28, 2022 Cloudflare		Expires: July 6, 2022 Cloudflare
	November 24, 2021		January 02, 2022
	Binary Representation of HTTP Messages		Binary Representation of HTTP Messages
	draft-ietf-httpbis-binary-message-00		draft-ietf-httpbis-binary-message-latest
	Abstract		Abstract
	This document defines a binary format for representing HTTP messages.		This document defines a binary format for representing HTTP messages.
	Discussion Venues		About This Document
	This note is to be removed before publishing as an RFC.		This note is to be removed before publishing as an RFC.
			Status information for this document may be found at
			<https://datatracker.ietf.org/doc/draft-ietf-httpbis-binary-
			message/>.
	Discussion of this document takes place on the HTTP Working Group		Discussion of this document takes place on the HTTP Working Group
	mailing list (ietf-http-wg@w3.org), which is archived at		mailing list (<mailto:ietf-http-wg@w3.org>), which is archived at
	<https://lists.w3.org/Archives/Public/ietf-http-wg/>.		<https://lists.w3.org/Archives/Public/ietf-http-wg/>. Working Group
			information can be found at <https://httpwg.org/>.
			Source for this draft and an issue tracker can be found at
			<https://github.com/httpwg/http-extensions/labels/binary-messages>.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on May 28, 2022.		This Internet-Draft will expire on July 6, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
	3. Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3.1. Known Length Messages . . . . . . . . . . . . . . . . . . 4
	3.2. Indeterminate Length Messages . . . . . . . . . . . . . . 5
	3.3. Framing Indicator . . . . . . . . . . . . . . . . . . . . 6
	3.4. Request Control Data . . . . . . . . . . . . . . . . . . 6
	3.5. Response Control Data . . . . . . . . . . . . . . . . . . 7
	3.5.1. Informational Status Codes . . . . . . . . . . . . . 7
	3.6. Header and Trailer Field Lines . . . . . . . . . . . . . 8
	3.7. Content . . . . . . . . . . . . . . . . . . . . . . . . . 9
	4. Invalid Messages . . . . . . . . . . . . . . . . . . . . . . 9
	5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	5.1. Request Example . . . . . . . . . . . . . . . . . . . . . 9
	5.2. Response Example . . . . . . . . . . . . . . . . . . . . 10
	6. "message/bhttp" Media Type . . . . . . . . . . . . . . . . . 13
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
	9.1. Normative References . . . . . . . . . . . . . . . . . . 14
	9.2. Informative References . . . . . . . . . . . . . . . . . 15
	9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 15
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	1. Introduction		1. Introduction
	This document defines a simple format for representing an HTTP		This document defines a simple format for representing an HTTP
	message ([HTTP]), either request or response. This allows for the		message ([HTTP]), either request or response. This allows for the
	encoding of HTTP messages that can be conveyed outside of an HTTP		encoding of HTTP messages that can be conveyed outside of an HTTP
	protocol. This enables the transformation of entire messages,		protocol. This enables the transformation of entire messages,
	including the application of authenticated encryption.		including the application of authenticated encryption.
	This format is informed by the framing structure of HTTP/2 ([H2]) and		This format is informed by the framing structure of HTTP/2 ([H2]) and
	HTTP/3 ([H3]). In comparison, this format simpler by virtue of not		HTTP/3 ([H3]). In comparison, this format simpler by virtue of not
End of changes. 8 change blocks.
	35 lines changed or deleted		16 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/