Re: Issue with "bytes" Range Unit and live streaming
Darshak Thakore <d.thakore@cablelabs.com> Fri, 15 April 2016 21:15 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 C3C3812D9E9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 14:15:07 -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 J7VjChqsC_oX for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 15 Apr 2016 14:15:04 -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 3E5BD12D6E8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 15 Apr 2016 14:15:04 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1arB0U-0000gs-ND for ietf-http-wg-dist@listhub.w3.org; Fri, 15 Apr 2016 21:10:26 +0000
Resent-Date: Fri, 15 Apr 2016 21:10:26 +0000
Resent-Message-Id: <E1arB0U-0000gs-ND@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 <d.thakore@cablelabs.com>) id 1arB0Q-0000fK-OR for ietf-http-wg@listhub.w3.org; Fri, 15 Apr 2016 21:10:22 +0000
Received: from ondar.cablelabs.com ([192.160.73.61]) by lisa.w3.org with esmtp (Exim 4.80) (envelope-from <d.thakore@cablelabs.com>) id 1arB0P-0001iO-Ai for ietf-http-wg@w3.org; Fri, 15 Apr 2016 21:10:22 +0000
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.7/8.14.7) with ESMTP id u3FL9niu012661; Fri, 15 Apr 2016 15:09:50 -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 15:09:49 -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 15:09:46 -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+8AgAAGnQCAAAUNgP//ov8A
Date: Fri, 15 Apr 2016 21:09:45 +0000
Message-ID: <D336B3B5.AC00%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> <6AB4CBAA-E79D-4DAC-818D-65383B85B81B@gbiv.com>
In-Reply-To: <6AB4CBAA-E79D-4DAC-818D-65383B85B81B@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_D336B3B5AC00dthakorecablelabscom_"
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: lisa.w3.org 1arB0P-0001iO-Ai b0a29afea61827ce16a7a1e43bf72794
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/D336B3B5.AC00%25d.thakore@cablelabs.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31489
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>
Oops, my earlier email got criss-crossed with this one. 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/* Oh, never mind, now I see that you are referring to the second number being fixed. I think I would prefer that be solved by allowing last-byte-pos to be empty, just like it is for the Range request. I think such a fix is just as likely to be interoperable as introducing a special range type (same failure cases). DT>> We would be ok with that approach too. Our initial thought was that it would be more invasive (less acceptable) so we opted for suggesting an alternate unit. That way we don’t break existing clients and any client that desires the “open-ended last-byte-pos” feature could support the new 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