Network Working Group M. Kerwin
Intended status: Standards Track August 18, 2014
Expires: February 19, 2015

HTTP/2 Encoded Data


This document introduces new frame types for transporting encoded data in HTTP/2, and an associated error code.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on February 19, 2015.

Copyright Notice

Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

1. Introduction

This document introduces a mechanism for applying encoding, particularly compression, to data transported between two HTTP/2 endpoints, analogous to Transfer-Encoding in HTTP/1.1 [RFC7230].

1.1. Notational Conventions

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].

2. Additions to HTTP/2

This document introduces two new HTTP/2 frame types ([I-D.ietf-httpbis-http2], Section 11.2) and a new HTTP/2 error code ([I-D.ietf-httpbis-http2], Section 7), to allow the application of encoding, particularly compression, to data.

Note that while encoding some or all data in a stream might affect the total length of the corresponding HTTP message body, the content-length header, if present, should continue to reflect the total length of the unencoded data. This is particularly relevant when detecting malformed messages ([I-D.ietf-httpbis-http2], Section


An ACCEPT_ENCODED_DATA frame (type code=0xTBA) is used to indicate the sender’s ability and willingness to receive ENCODED_DATA frames that are encoded using the schemes identified in its payload.

The payload length of an ACCEPT_ENCODED_DATA frame MUST be an exact multiple of 16 bits (2 bytes). An endpoint that receives an ACCEPT_ENCODED_DATA frame with an odd length MUST treat this as a connection error ([I-D.ietf-httpbis-http2], Section 5.4.1) of type PROTOCOL_ERROR.

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  | Encoding (8)  |   Rank (8)    | ...


The ACCEPT_ENCODED_DATA frame contains zero or more tuples comprising the following fields:

The rank fulfils the same role as in the HTTP/1.1 TE header ([RFC7230], Section 4.3). The rank value is an integer in the range 0 through 255, where 1 is the least preferred and 255 is the most preferred; a value of 0 means “not acceptable”.

An endpoint that receives an ACCEPT_ENCODED_DATA frame containing an {encoding,rank} tuple with an unknown or unsupported encoding identifier MUST ignore that tuple.

Each ACCEPT_ENCODED_DATA frame fully replaces the set of tuples sent in a previous frame; if an encoding identifier is omitted from a subsequent ACCEPT_ENCODED_DATA frame it is deemed “not acceptable”.

An endpoint may advertise support for an encoding scheme and later decide that it no longer supports that scheme. After sending an ACCEPT_ENCODED_DATA that omits the encoding identifier in question, or includes it with a rank of 0, the endpoint SHOULD continue to accept ENCODED_DATA frames using that scheme for a reasonable amount of time to account for encoded frames that are already in flight.

The ACCEPT_ENCODED_DATA frame does not define any flags, and is not subject to flow control.


ENCODED_DATA frames (type code=0xTBA) are semantically identical to DATA frames ([I-D.ietf-httpbis-http2], Section 6.1), but have an encoding applied to their payload. Significantly, ENCODED_DATA frames are subject to flow control ([I-D.ietf-httpbis-http2], Section 5.2).

Any encoding or decoding context for an ENCODED_DATA frame is unique to that frame.

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  |Pad Length? (8)|
  | Encoding (8)  |
  |                            Data (*)                         ...
  |                           Padding (*)                       ...

ENCODED_DATA Frame Payload

The ENCODED_DATA frame contains the following fields:

The ENCODED_DATA frame defines the following flags:

On receiving an ENCODED_DATA frame, an intermediary MAY decode the data and forward it in one or more DATA frames. If the downstream peer does not support the encoding scheme used in the received frame, as advertised in an ACCEPT_ENCODED_DATA frame, the intermediary MUST decode the data and either: forward it in one or more DATA frames, or encode it with a scheme supported by the downstream peer and forward it in one or more ENCODED_DATA frames.

An ENCODED_DATA frame MUST NOT be sent on a connection before receiving an ACCEPT_ENCODED_DATA frame. A sender MUST NOT apply an encoding that has not first been advertised by the peer in an ACCEPT_ENCODED_DATA frame, or was advertised with a rank of 0. Endpoints that receive a frame with an encoding they do not recognise or support MUST treat this as a connection error of type PROTOCOL_ERROR.

If an endpoint detects that the payload of an ENCODED_DATA frame is incorrectly encoded it MUST treat this as a stream error (see [I-D.ietf-httpbis-http2], Section 5.4.2) of type DATA_ENCODING_ERROR (Section 2.3).

ENCODED_DATA frames are subject to flow control and can only be sent when a stream is in the “open” or “half closed (remote)” states. The entire ENCODED_DATA frame payload is included in flow control, including the encoded data, and Pad Length and Padding fields if present. If an ENCODED_DATA frame is received whose stream is not in “open” or “half closed (local)” state, the recipient MUST respond with a stream error ([I-D.ietf-httpbis-http2], Section 5.4.2) of type STREAM_CLOSED.

2.2.1. Fragmentation and Segments

Traversing a network segment with small frame size restrictions introduces the risk of fragmenting an encoded stream. This can be avoided using segments, as defined in [I-D.kerwin-http2-segments].

An intermediary MAY coalesce multiple adjacent ENCODED_DATA and DATA frames if all of the frames, with the optional exception of the final frame in the sequence, have the SEGMENT_CONTINUES flag set. The coalesced payload MAY be subsequently emitted in any combination of ENCODED_DATA and DATA frames. The payloads of any resulting ENCODED_DATA frame MUST be correctly encoded according to those frames’ encodings; note that this could require the payloads of the original frames to be decoded and subsequently re-encoded into the new frames, rather than simply concatenated.


The following new error code is defined:

3. Encoding Schemes

The following encoding schemes are defined:

4. Security Considerations

Further to the Use of Compression in HTTP/2 ([I-D.ietf-httpbis-http2], Section 10.6), intermediaries MUST NOT apply compression to DATA frames, or alter the compression of ENCODED_DATA frames other than decompressing, unless additional information is available that allows the intermediary to identify the source of data. In particular, frames that are not compressed cannot be compressed, and frames that are separately compressed can only be merged into a single compressed frame if they occupy the same segment.

5. IANA Considerations

This document updates the registries for frame types and error codes in the “Hypertext Transfer Protocol (HTTP) 2 Parameters” section. This document also establishes a new registry for HTTP/2 encoding scheme codes. This new registry is entered into the “Hypertext Transfer Protocol (HTTP) 2 Parameters” section.

5.1. HTTP/2 Frame Type Registry Update

This document updates the “HTTP/2 Frame Type” registry ([I-D.ietf-httpbis-http2], Section 11.2). The entries in the following table are registered by this document.

Frame Type Code Section

5.2. HTTP/2 Error Code Registry Update

This document updates the “HTTP/2 Error Code” registry ([I-D.ietf-httpbis-http2], Section 11.4). The entries in the following table are registered by this document.

Name Code Description Specification
DATA_ENCODING_ERROR TBD Invalid encoding detected Section 2.3

5.3. HTTP/2 Encoding Schemes Registry

This document establishes a registry for encoding scheme codes. The “HTTP/2 Encoding Schemes” registry manages an 8-bit space. The “HTTP/2 Encoding Schemes” registry operates under either of the “IETF Review” or “IESG Approval” policies [RFC5226] for values between 0x00 and 0xef, with values between 0xf0 and 0xff being reserved for experimental use.

New entries in this registry require the following information:

An initial set of encoding scheme code registrations can be found in Section 3.

6. Acknowledgements

Thanks to Keith Morgan for his advice, input, and editorial contributions.

7. References

7.1. Normative References

[I-D.ietf-httpbis-http2] Belshe, M., Peon, R. and M. Thomson, "Hypertext Transfer Protocol version 2", Internet-Draft draft-ietf-httpbis-http2-14, July 2014.
[I-D.kerwin-http2-segments] Kerwin, M., "HTTP/2 Segments", Internet-Draft draft-kerwin-http2-segments-00, July 2014.
[RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data Format Specification version 3.3", RFC 1950, May 1996.
[RFC1951] Deutsch, P., "DEFLATE Compressed Data Format Specification version 1.3", RFC 1951, May 1996.
[RFC1952] Deutsch, P., Gailly, J-L., Adler, M., Deutsch, L. and G. Randers-Pehrson, "GZIP file format specification version 4.3", RFC 1952, May 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[Welch] Welch, T., "A Technique for High-Performance Data Compression", IEEE Computer 17(6), June 1984.

7.2. Informative References

[RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, June 2014.

Author's Address

Matthew Kerwin EMail: URI: