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

Document Type Active Internet-Draft (httpbis WG)
Last updated 2017-03-07
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HTTP Working Group                                              C. Pratt
Internet-Draft                                                 CableLabs
Intended status: Experimental                                   B. Stark
Expires: September 8, 2017                                          AT&T
                                                              D. Thakore
                                                               CableLabs
                                                           March 7, 2017

                  HTTP Random Access and Live Content
                 draft-ietf-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.

Editorial Note (To be removed by RFC Editor before publication)

   Discussion of this draft takes place on the HTTPBIS working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   <https://lists.w3.org/Archives/Public/ietf-http-wg/>.

   Working Group information can be found at <http://httpwg.github.io/>;
   source code and issues list for this draft can be found at
   <https://github.com/httpwg/http-extensions/labels/rand-access-live>.

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 September 8, 2017.

Pratt, et al.           Expires September 8, 2017               [Page 1]
Internet-Draft            http-rand-access-live               March 2017

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Performing Range requests on Random-Access Aggregating
       ("live") Content  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Establishing the Randomly Accessible Byte Range . . . . .   4
     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  . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

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
Show full document text