HTTP Random Access and Live Content
draft-pratt-httpbis-rand-access-live-00

Document Type Active Internet-Draft (individual)
Last updated 2016-11-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Hypertext Transfer Protocol                                     C. Pratt
Internet-Draft                                                 CableLabs
Intended status: Informational                                  B. Stark
Expires: May 17, 2017                                               AT&T
                                                              D. Thakore
                                                               CableLabs
                                                       November 13, 2016

                  HTTP Random Access and Live Content
                draft-pratt-httpbis-rand-access-live-00

Abstract

   To accommodate byte range requests for content that has data appended
   over time, this document defines semantics that allow a HTTP client
   and server to perform byte-range GET and HEAD requests that start at
   an arbitrary byte offset within the representation and ends at an
   indeterminate offset.

Requirements Language

   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 RFC 2119 [RFC2119].

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 May 17, 2017.

Copyright Notice

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

Pratt, et al.             Expires May 17, 2017                  [Page 1]
Internet-Draft            http-rand-access-live            November 2016

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Performing Range requests on Random-Access Aggregating
       ("live") Content  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Establishing the Randomly Accessible Byte Range . . . . .   3
     2.2.  Byte-Range Requests Beyond the Randomly Accessible Byte
           Range . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Byte-Range Responses Beyond the Randomly Accessible Byte
           Range . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Other Applications of Random-Access Aggregating Content . . .   6
     3.1.  Requests Starting at the Aggregation ("Live") Point . . .   6
     3.2.  Shift Buffer Representations  . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Some Hypertext Transfer Protocol (HTTP) Clients use byte-range
   requests (Range requests using the "bytes" Range Unit) to transfer
   select portions of large representations.  And in some cases large
   representations require content to be continuously or periodically
   appended - such as representations consisting of live audio or video
   sources, blockchain databases, and log files.  Clients cannot access
   the appended/live content using a Range request with the bytes range
   unit using the currently defined byte-range semantics accepting
   performance or behavior sacrifices which are not acceptable for many
   applications.

   For instance, HTTP Clients have the ability to access appended
Show full document text