- From: STARK, BARBARA H <bs7652@att.com>
- Date: Mon, 14 Nov 2016 08:34:09 +0000
- To: HTTP Working Group <ietf-http-wg@w3.org>
Sorry this draft didn't get uploaded by Oct 31, but there were, um, technical difficulties. This is on the agenda for Thursday, and is an alternate proposal for handling the problem of doing range requests on live content (where the endpoint is increasing). The previous draft (draft-pratt-httpbis-bytes-live-range-unit-00) had suggested a new "bytes-live" range unit. Based on very helpful discussion, we have a new draft that proposes no changes to the HTTP protocol, but does propose using very large endpoint values to indicate a request for and response that provides content up to wherever the live point is, and continues to provide content as the live point increases.
Barbara
-----Original Message-----
A new version of I-D, draft-pratt-httpbis-rand-access-live-00.txt
has been successfully submitted by Craig Pratt and posted to the IETF repository.
Name: draft-pratt-httpbis-rand-access-live
Revision: 00
Title: HTTP Random Access and Live Content
Document date: 2016-11-13
Group: Individual Submission
Pages: 9
URL: https://www.ietf.org/internet-drafts/draft-pratt-httpbis-rand-access-live-00.txt
Status: https://datatracker.ietf.org/doc/draft-pratt-httpbis-rand-access-live/
Htmlized: https://tools.ietf.org/html/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.
Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
Received on Monday, 14 November 2016 08:34:56 UTC