IETF Logo Mail Archive

RE: Issue with "bytes" Range Unit and live streaming

<K.Morgan@iaea.org> Mon, 18 April 2016 07:39 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 63D6412DE48 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 18 Apr 2016 00:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.917
X-Spam-Level:
X-Spam-Status: No, score=-7.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=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 UzpT0bDZEvQL for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 18 Apr 2016 00:39:21 -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 3628C12D620 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 18 Apr 2016 00:39:20 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1as3hv-00014K-Oq for ietf-http-wg-dist@listhub.w3.org; Mon, 18 Apr 2016 07:34:55 +0000
Resent-Date: Mon, 18 Apr 2016 07:34:55 +0000
Resent-Message-Id: <E1as3hv-00014K-Oq@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 <K.Morgan@iaea.org>) id 1as3hq-00013Z-L7 for ietf-http-wg@listhub.w3.org; Mon, 18 Apr 2016 07:34:50 +0000
Received: from vs-m201.iaea.org ([161.5.6.178]) by maggie.w3.org with esmtp (Exim 4.80) (envelope-from <K.Morgan@iaea.org>) id 1as3ho-0004gk-K2 for ietf-http-wg@w3.org; Mon, 18 Apr 2016 07:34:50 +0000
Received: from vs-m1.iaea.org (vs-mail1.iaea.org [172.24.1.26]) by vs-m201.iaea.org (8.14.9/8.14.3/SuSE Linux 0.8) with ESMTP id u3I7YAmg021728; Mon, 18 Apr 2016 09:34:12 +0200
Received: from E1.iaea.org (e1.iaea.org [172.24.0.41]) by vs-m1.iaea.org (8.14.9/8.14.3/SuSE Linux 0.8) with ESMTP id u3I7Y8EN015201; Mon, 18 Apr 2016 09:34:08 +0200
X-Envelope-Sender: K.Morgan@iaea.org
Received: from SEM002PD.sg.iaea.org (161.5.105.93) by E1.iaea.org (172.24.0.41) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 18 Apr 2016 09:34:07 +0200
Received: from SEM001PD.sg.iaea.org ([169.254.1.55]) by SEM002PD.sg.iaea.org ([169.254.2.133]) with mapi id 14.03.0224.002; Mon, 18 Apr 2016 09:34:07 +0200
From: K.Morgan@iaea.org
To: fielding@gbiv.com, craig@ecaspia.com
CC: goran.ap.eriksson@ericsson.com, bs7652@att.com, remy@lebeausoftware.org, ietf-http-wg@w3.org, rodger@plexapp.com, julian.reschke@gmx.de, C.Brunhuber@iaea.org
Thread-Topic: Issue with "bytes" Range Unit and live streaming
Thread-Index: AQHRlqXe1GjhLG2FVUuO4qvJ5GIp1Z+KGy8AgADHwACAAGFaAIAAD+8AgAAGnQCAAAUNgIAD9nbA
Date: Mon, 18 Apr 2016 07:34:06 +0000
Message-ID: <0356EBBE092D394F9291DA01E8D28EC2021CEBE9AC@SEM001PD.sg.iaea.org>
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-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.5.105.94]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KLMS-Rule-ID: 1
X-KLMS-Message-Action: clean
X-KLMS-AntiSpam-Status: not_detected
X-KLMS-AntiPhishing: Clean, 2016/04/15 08:21:31
X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, bases: 2016/04/17 23:27:00 #7565430; khse: 2014-01-23 rollback
X-KLMS-AntiVirus-Status: Clean, skipped
X-Scanned-By: MIMEDefang 2.73 on 172.24.1.26
X-KLMS-AntiSpam-Lua-Profiles: 94882 [Apr 18 2016]
X-KLMS-AntiSpam-Version: 5.5.9.33
X-KLMS-AntiSpam-Envelope-From: K.Morgan@iaea.org
X-KLMS-AntiSpam-Rate: 0
X-KLMS-AntiSpam-Method: none
X-KLMS-AntiSpam-Info: LuaCore: 429 429 6a1508c87bf68f13be0465c30886f11be0a06ffa, Auth:dkim=none
X-KLMS-AntiSpam-Interceptor-Info: scan successful
Received-SPF: pass client-ip=161.5.6.178; envelope-from=K.Morgan@iaea.org; helo=vs-m201.iaea.org
X-W3C-Hub-Spam-Status: No, score=-5.8
X-W3C-Hub-Spam-Report: AWL=-1.053, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, W3C_NW=0.5
X-W3C-Scan-Sig: maggie.w3.org 1as3ho-0004gk-K2 f88e1d44d180964b9ecdb7fc75c2d9d5
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/0356EBBE092D394F9291DA01E8D28EC2021CEBE9AC@SEM001PD.sg.iaea.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31491
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 Friday,15 April 2016 22:43, fielding@gbiv.com wrote:
> 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).
>
> ....Roy

+1000

A very similar idea was proposed before [1] as an I-D [2] by Rodger Coombs. We've also brought this up informally with other members of the WG.

Alas, in our experience range requests don't seem to be a high priority :(  For example, the problem of combining gzip with range requests is still unsolved [3].

[1] https://lists.w3.org/Archives/Public/ietf-http-wg/2015AprJun/0122.html
[2] https://tools.ietf.org/html/draft-combs-http-indeterminate-range-01
[3] https://lists.w3.org/Archives/Public/ietf-http-wg/2014AprJun/1327.html


This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.

v2.23.0 | Report a Bug | By Email