HTTP/2 Segments
draft-kerwin-http2-segments-00

Abstract

This document introduces the concept of “segments” to HTTP/2, and adds a flag to the DATA frame type to allow the expression segments.

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 http://datatracker.ietf.org/drafts/current/.

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 January 28, 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 (http://trustee.ietf.org/license-info) 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
• 1.1. Notational Conventions
• 2. Segments
• 3. SEGMENT_CONTINUES Flag
• 4. Security Considerations
• 5. IANA Considerations
• 6. Normative References
• Author's Address

1. Introduction

This document extends HTTP/2 [I-D.ietf-httpbis-http2] by introducing the concept of “segments” to HTTP/2, as a mechanism to combat the effects of fragmentation within a stream. It does this by adding a new flag to the DATA frame type ([I-D.ietf-httpbis-http2], Section 6.1).

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. Segments

A “segment” is a contiguous region of a HTTP/2 message’s payload data which can be freely fragmented and recombined. A segment is expressed by marking all but the final frame in the segment with the SEGMENT_CONTINUES flag (Section 3). Any data-bearing frame that does not have the SEGMENT_CONTINUES flag set, and does not follow one that does, comprises a single segment.

Segments can be used to mitigate the effects of fragmentation within a stream. For example, an endpoint may have a large chunk of data which it has to transmit via multiple DATA frames in order to comply with frame size limits. It can mark those frames as a single segment so that any downstream peer without the same frame size restrictions knows that it can safely coalesce the frames.

3. SEGMENT_CONTINUES Flag

The following new flag is defined for the DATA frame ([I-D.ietf-httpbis-http2], Section 6.1):

• SEGMENT_CONTINUES (0x10): Bit 5 being set indicates that the current segment continues after the current frame (see Section 2). Intermediaries MUST NOT coalesce frames across a segment boundary and MUST preserve segment boundaries when forwarding frames.

4. Security Considerations

5. IANA Considerations

This document has no actions for IANA.

6. Normative References

Author's Address