Re: Specifying Range in Link preload header for HTTP/2 Push?

Julian Reschke <julian.reschke@gmx.de> Fri, 12 July 2019 17:32 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 5ADC51203C2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 12 Jul 2019 10:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level:
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 PaDzkKYHph9J for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 12 Jul 2019 10:32:54 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8E9D120310 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 12 Jul 2019 10:32:54 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hlzNc-0006gC-H6 for ietf-http-wg-dist@listhub.w3.org; Fri, 12 Jul 2019 17:30:44 +0000
Resent-Date: Fri, 12 Jul 2019 17:30:44 +0000
Resent-Message-Id: <E1hlzNc-0006gC-H6@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <julian.reschke@gmx.de>) id 1hlzNa-0006fQ-MH for ietf-http-wg@listhub.w3.org; Fri, 12 Jul 2019 17:30:42 +0000
Received: from mout.gmx.net ([212.227.17.21]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <julian.reschke@gmx.de>) id 1hlzNY-0006nP-72 for ietf-http-wg@w3.org; Fri, 12 Jul 2019 17:30:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1562952614; bh=cNDacDsKSi0LBbGE84ONhzGxNdlPNb89URPKysNn+NA=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=VUp6nd1fzObE0xJj9l5+4JXye1vnCsQn8FI/dr1EtSdKb1qwjKWC6o4ld6vULiGTp nAHtm8vGKt7UYOH6TjueFF66C0A+5axF6+4Gnc9k3EcB8PYsBFeNtqD1QOtgwB1Qow e8lf8wM5AYl+96+LoW5IkaVI+vOWZ84ACxx2mKrI=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.151.199]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M2O6Y-1hlRwO2WAo-003vmH; Fri, 12 Jul 2019 19:30:14 +0200
To: Roger Pantos <rpantos@apple.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
References: <63CAE7E1-34E9-42DA-A7DD-1E17223032AE@apple.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <06f5a4ad-099a-87a8-9e26-ccc5132b963c@gmx.de>
Date: Fri, 12 Jul 2019 19:30:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <63CAE7E1-34E9-42DA-A7DD-1E17223032AE@apple.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:kQ44tDE5qqOvcPiD3R9/HHwqaz99E4SUAwt5+vc1UhGkuxQu2KQ nSSb4wAUPo0+e2TCFV3yL+UYDpIXaIVneFFGv9CpPTVwfmQjdfyptElBCeZO+eCSt7aAuYe HArCdav5ZLRTEJj5x1TE1M8o09jLuMk8Hyc+OCp86kFvJ8hDPEFFM3Atu1WxgUJmVCRZbMm YqkAhTuEjue9pW9CNomxA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:+LE+S6tOeCs=:6KK6rnjCwR6UnGqM1Y4Zzb Gc5pafOiKRixOBAK/HoNYJ6xj5XTy2+cyKr5DZ6eIZHyaEu2evh+f/SQKbdjiG02TjVouWVQi ALtfSpMV5ik08W1CO4CKzCP4YPXvcNZSO11DbSVNpODZ9k4mZ4gDkpE90L2pF/H3VpuKXRqjD YffJgzh4gFb0OmhhwP3QV88e62X7lZ7KskivZc3Vsu6yT8bOtodfJaNF3NxgICCFgQii2HMvv jFGFmh1AJ+k928PnitaIOMkOZtf6UknNPQ+gAzTNgrq4PXdcHX4eIJIor4nqLkF+Suz8fhYYy QchKHkHWQjFVNhoDy/yCHqZdKUjjuHBtjchX5QmxYAXehMZQhKD95RYdueWsAXHNC1I9wXl1h 0jM+WkiIgmvmtb868H+HeDSskIuPZmOpL4az8/MzWA6bGrOL8vK+g56m0EqQg4UAciRBae9OC jvf2LrFNNxe5quPFUPsNKBJ5xhaMtTUh0aR8h703+UPggcPC+IBOo/eLdZfEy/11HSHeDlwLX 4sHUxzvPfEJz1AycdBAdiYdAXQuhQy2QuOGZl+tPFA/ExHq+k5kJgwZdKCXuoTqBxRqXVtCz8 9j5eRWlscO2Dft2nx89ShjZ75CyijO0plvUy4rBtrBczmkS5vyvnHkunMA2glXAxxkV400FGn MYS1WnXbaAY+EMVoV5T6DDRhl6SA/QvPEvOnGgNEr9+v9mgFz/NIC6KBeG1tlHplBsWOSbE/h PL/6MC3PHKPDE6FQ8MghplK/iYsa8CvznfjAsHynmzuDj/eKtPOQ6m7oE3yL23JN01Yc0TXbM F1LKtEWnULi8YT9Q7WUCFsyT7WBXjV/zjTE/jg5o68nDgEhYSD1HQ2wDC4vFzd6mL2BPup4Zp XrQy1nzDJ40pn5xHvwGX2m/axznoHaAbcltu52E/RB02gl34tasV42EBAYImlW4zQXC4GgzWY Wzf6cMKW9k85O5vvFkO9dxTAZDx+xj9GZIS/FA3zj0+iTvrWU+SELlv4k1ER8tLSMKijp4AH/ dLTd3ed6Pbglfthq/f+YH7jQbK5Pn9CpP4tBvf/+yOmicCtS4u2xNXwIzxtu2LuiYXXWkG4KL nfTiEyT3jJoGG0w8msGxUwHg2HH0Q8dKtqX
Received-SPF: pass client-ip=212.227.17.21; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: AWL=2.351, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1hlzNY-0006nP-72 93b9f35febaf69c144bb59582e592b9a
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Specifying Range in Link preload header for HTTP/2 Push?
Archived-At: <https://www.w3.org/mid/06f5a4ad-099a-87a8-9e26-ccc5132b963c@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36795
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 09.07.2019 18:55, Roger Pantos wrote:
> Greetings HTTP experts,
>
> I’m interested in employing HTTP/2 Push of Range requests for media streaming. It seems like the core h2 protocol handles this well enough; the PUSH_PROMISE can contain a Range header, and at the very least if that ends up in the client push cache then a request for that exact Range should match.
>
> That being said, I’d also like to signal the push request to downstream HTTP caches. Push is typically signaled via the Link header with rel=preload, but https://www.w3.org/TR/preload/ doesn’t seem to define signaling and associated Range.
>
> Has anyone defined a Link extension to signal an associated Range?
>
> If not, would anyone object to the following Link extension?
>
> range-link-extension = “range” = ranges-specifier
>
> where ranges-specifier is defined in RFC 2616.
>
> An example would be:
>
> Link: </media.mp4>; rel=preload; as=video; type=video/mp4; range=1380-14226
> ...

Nitpicking: if you do this, please consider range units other than
"bytes".  For instance, by embedding the range unit name into the parameter:

Link: </media.mp4>; rel=preload; as=video; type=video/mp4;
range-bytes=1380-14226

Best regards, Julian