Re: Issue with "bytes" Range Unit and live streaming
Darshak Thakore <d.thakore@cablelabs.com> Fri, 15 April 2016 21:04 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 B0E8A12E389 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 14:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.916
X-Spam-Level:
X-Spam-Status: No, score=-7.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 7kYQrYNaYQCW for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 14:04:51 -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 71F0512E385 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 15 Apr 2016 14:04:51 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1arAqn-00059d-0x for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Apr 2016 21:00:25 +0000
Resent-Date: Fri, 15 Apr 2016 21:00:25 +0000
Resent-Message-Id: <E1arAqn-00059d-0x@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <d.thakore@cablelabs.com>) id 1arAqi-00058s-Jd for ietf-http-wg@listhub.w3.org; Fri, 15 Apr 2016 21:00:20 +0000
Received: from ondar.cablelabs.com ([192.160.73.61]) by maggie.w3.org with esmtp (Exim 4.80) (envelope-from <d.thakore@cablelabs.com>) id 1arAqg-0001Qq-OE for ietf-http-wg@w3.org; Fri, 15 Apr 2016 21:00:19 +0000
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.7/8.14.7) with ESMTP id u3FKxlsX011828; Fri, 15 Apr 2016 14:59:47 -0600
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Fri, 15 Apr 2016 14:59:46 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([::1]) by EXCHANGE.cablelabs.com ([::1]) with mapi id 14.03.0266.001; Fri, 15 Apr 2016 14:59:43 -0600
From: Darshak Thakore <d.thakore@cablelabs.com>
To: "Roy T. Fielding" <fielding@gbiv.com>, Craig Pratt <craig@ecaspia.com>
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>
Thread-Topic: Issue with "bytes" Range Unit and live streaming
Thread-Index: AQHRlqXQTxw2V0NQf0KoUQ9o5MKxop+KoUsAgADHwACAAGFaAIAAD+8AgAAGnQD//6U+AA==
Date: Fri, 15 Apr 2016 20:59:42 +0000
Message-ID: <D336B231.ABFC%d.thakore@cablelabs.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> <43C1ECE7-139E-4FC8-A46D-83887261B7BC@gbiv.com>
In-Reply-To: <43C1ECE7-139E-4FC8-A46D-83887261B7BC@gbiv.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-originating-ip: [10.5.0.27]
Content-Type: multipart/alternative; boundary="_000_D336B231ABFCdthakorecablelabscom_"
MIME-Version: 1.0
X-Approved: ondar
Received-SPF: pass client-ip=192.160.73.61; envelope-from=d.thakore@cablelabs.com; helo=ondar.cablelabs.com
X-W3C-Hub-Spam-Status: No, score=-9.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1arAqg-0001Qq-OE 3ecdd559f176ce0c79e1efb42bd59a5c
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/D336B231.ABFC%25d.thakore@cablelabs.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31487
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 4/15/16, 2:24 PM, "Roy T. Fielding" <fielding@gbiv.com<mailto:fielding@gbiv.com>> wrote: On Apr 15, 2016, at 1:00 PM, Craig Pratt <craig@ecaspia.com<mailto: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/* DT>> The issue we have is with specifying 1233 as the last-byte-pos since that will change as soon as it is set. 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