Re: Issue with "bytes" Range Unit and live streaming
"Roy T. Fielding" <fielding@gbiv.com> Fri, 15 April 2016 20:29 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C40D312DEC7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 13:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.016
X-Spam-Level:
X-Spam-Status: No, score=-8.016 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDzCCi2MGxRC for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 13:29:37 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39E8B12D8FB for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 15 Apr 2016 13:29:37 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1arAIa-0005Qy-2Q for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Apr 2016 20:25:04 +0000
Resent-Date: Fri, 15 Apr 2016 20:25:04 +0000
Resent-Message-Id: <E1arAIa-0005Qy-2Q@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <fielding@gbiv.com>) id 1arAIW-0004HM-5l for ietf-http-wg@listhub.w3.org; Fri, 15 Apr 2016 20:25:00 +0000
Received: from sub4.mail.dreamhost.com ([69.163.253.135] helo=homiemail-a24.g.dreamhost.com) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <fielding@gbiv.com>) id 1arAIU-00080z-N9 for ietf-http-wg@w3.org; Fri, 15 Apr 2016 20:24:59 +0000
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id F37DA2C80CD; Fri, 15 Apr 2016 13:24:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc:message-id :references:to; s=gbiv.com; bh=BQwd4kfwYuxmqAtJFYKlr4bXumU=; b=O IrLLfzaaqn4UHfDPYmIORN1s+oJcG2KkI7MARzaPsN0No4wuha/ZqOUv4SDwFnTS NZXlBzbJcdn/6h2SSbyOr9bEql9CKVWthV+ZwoD78twtN8j5YxBissI4H5o1bPN1 YFcxj/VGOLaL+Z72ydi4J8DxKgb0he/blRpwUapAOE=
Received: from [192.168.1.2] (ip68-228-71-159.oc.oc.cox.net [68.228.71.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id BBADF2C80AD; Fri, 15 Apr 2016 13:24:34 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F66CDD00-F0BE-496C-9FD1-F7E68AD548B8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <57114878.1030606@ecaspia.com>
Date: Fri, 15 Apr 2016 13:24:36 -0700
Cc: Göran Eriksson AP <goran.ap.eriksson@ericsson.com>, "STARK, BARBARA H" <bs7652@att.com>, Remy Lebeau <remy@lebeausoftware.org>, IETF HTTP BIS <ietf-http-wg@w3.org>
Message-Id: <43C1ECE7-139E-4FC8-A46D-83887261B7BC@gbiv.com>
References: <57102718.7010900@ecaspia.com> <571041E0.5020401@lebeausoftware.org> <2D09D61DDFA73D4C884805CC7865E61142655F7B@GAALPA1MSGUSRBF.ITServices.sbc.com> <D3370313.258AE%goran.ap.eriksson@ericsson.com> <57114878.1030606@ecaspia.com>
To: Craig Pratt <craig@ecaspia.com>
X-Mailer: Apple Mail (2.2104)
Received-SPF: none client-ip=69.163.253.135; envelope-from=fielding@gbiv.com; helo=homiemail-a24.g.dreamhost.com
X-W3C-Hub-Spam-Status: No, score=-6.7
X-W3C-Hub-Spam-Report: AWL=0.035, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1arAIU-00080z-N9 49d9c72a61b865ca074c67817af6c1d3
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Issue with "bytes" Range Unit and live streaming
Archived-At: <http://www.w3.org/mid/43C1ECE7-139E-4FC8-A46D-83887261B7BC@gbiv.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31485
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
> On Apr 15, 2016, at 1:00 PM, Craig Pratt <craig@ecaspia.com> wrote: > [cp] Remy answered this: Content-Length is not expressly required (since that would prevent chunked and other transfer encodings). But the Content-Range header can only communicate a fixed response. That is incorrect. See RFC7233, Sec 4.2: For byte ranges, a sender SHOULD indicate the complete length of the representation from which the range has been extracted, unless the complete length is unknown or difficult to determine. An asterisk character ("*") in place of the complete-length indicates that the representation length was unknown when the header field was generated. The following example illustrates when the complete length of the selected representation is known by the sender to be 1234 bytes: Content-Range: bytes 42-1233/1234 and this second example illustrates when the complete length is unknown: Content-Range: bytes 42-1233/* There is no need for another range unit. ....Roy
- Issue with "bytes" Range Unit and live streaming Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Remy Lebeau
- Re: Issue with "bytes" Range Unit and live stream… Amos Jeffries
- RE: Issue with "bytes" Range Unit and live stream… STARK, BARBARA H
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Göran Eriksson AP
- Re: Issue with "bytes" Range Unit and live stream… Remy Lebeau
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Göran Eriksson AP
- Re: Issue with "bytes" Range Unit and live stream… Göran Eriksson AP
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Roy T. Fielding
- Re: Issue with "bytes" Range Unit and live stream… Roy T. Fielding
- Re: Issue with "bytes" Range Unit and live stream… Darshak Thakore
- Re: Issue with "bytes" Range Unit and live stream… Remy Lebeau
- Re: Issue with "bytes" Range Unit and live stream… Darshak Thakore
- RE: Issue with "bytes" Range Unit and live stream… K.Morgan
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Mark Nottingham
- Re: Issue with "bytes" Range Unit and live stream… Mark Nottingham
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Roy T. Fielding
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Mark Nottingham
- Re: Issue with "bytes" Range Unit and live stream… Martin Thomson
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… Matthew Kerwin
- RE: Issue with "bytes" Range Unit and live stream… Matthew Kerwin
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Göran Eriksson AP
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… Thorsten Lohmar
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Roy T. Fielding
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- RE: Issue with "bytes" Range Unit and live stream… K.Morgan
- Re: Issue with "bytes" Range Unit and live stream… Darshak Thakore
- Re: Issue with "bytes" Range Unit and live stream… Mark Nottingham
- Re: Issue with "bytes" Range Unit and live stream… Adrien de Croy
- Re: Issue with "bytes" Range Unit and live stream… Martin Thomson
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Adrien de Croy
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt
- Re: Issue with "bytes" Range Unit and live stream… Adrien de Croy
- Re: Issue with "bytes" Range Unit and live stream… Julian Reschke
- Re: Issue with "bytes" Range Unit and live stream… Mark Nottingham
- Re: Issue with "bytes" Range Unit and live stream… Craig Pratt