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

Roger Pantos <rpantos@apple.com> Tue, 09 July 2019 20:35 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 363CF120025 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 9 Jul 2019 13:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.753
X-Spam-Level:
X-Spam-Status: No, score=-2.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 (2048-bit key) header.d=apple.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 mVde6utLgrBx for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 9 Jul 2019 13:35:32 -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 B2D4D120024 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 9 Jul 2019 13:35:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1hkwnN-0000io-Ol for ietf-http-wg-dist@listhub.w3.org; Tue, 09 Jul 2019 20:33:01 +0000
Resent-Date: Tue, 09 Jul 2019 20:33:01 +0000
Resent-Message-Id: <E1hkwnN-0000io-Ol@frink.w3.org>
Received: from uranus.w3.org ([128.30.52.58]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <rpantos@apple.com>) id 1hkwnM-0000h8-07 for ietf-http-wg@listhub.w3.org; Tue, 09 Jul 2019 20:33:00 +0000
Received: from www-data by uranus.w3.org with local (Exim 4.89) (envelope-from <rpantos@apple.com>) id 1hkwnL-00073o-RK for ietf-http-wg@listhub.w3.org; Tue, 09 Jul 2019 20:32:59 +0000
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 <rpantos@apple.com>) id 1hktRH-0005Kc-Ft for ietf-http-wg@listhub.w3.org; Tue, 09 Jul 2019 16:57:59 +0000
Received: from nwk-aaemail-lapp03.apple.com ([17.151.62.68]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <rpantos@apple.com>) id 1hktRF-0005Le-Os for ietf-http-wg@w3.org; Tue, 09 Jul 2019 16:57:59 +0000
Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x69GvE3i047263 for <ietf-http-wg@w3.org>; Tue, 9 Jul 2019 09:57:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : content-type : content-transfer-encoding : mime-version : date : subject : message-id : to; s=20180706; bh=KKpQYJWViXDQMfzfbNRqPoWpNroFFaNWjtJhPV8sEeM=; b=YeaH/dO9WfDouISuYaR6LKVMbgZYJX+BkbOYI3sn4zMbSGrXt6dUKbP71kH8o5o9jZwk NzHnW9B1YcCokuSDp8nlP6k+XZ2RZVyyUZ7GwtoivVeaOfqqIDWl+19V5/RNY2fbG2x3 Frkyv9UicOwmL8fFU4W6mCY9wz2QIbk0QUPVn+wc5FGDWJmTqzwqXAqLn81TD7xUtwz/ 6ZKGoj3EuNtC+ytIg8Sk416lpXVblxhCa8twaz6pywYAV/VPTYT5BKbgCuRcWTRhemBS UK/Gp07trJte/l5nfVi+JdD4w7HU+AA0s+jX9Ej2YnYjXNCkEWtYOdRA4qXoOAdzqJdh kw==
Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2tkbvkt86a-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <ietf-http-wg@w3.org>; Tue, 09 Jul 2019 09:57:36 -0700
Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0PUD00C2HWFZRQ30@ma1-mtap-s01.corp.apple.com> for ietf-http-wg@w3.org; Tue, 09 Jul 2019 09:57:36 -0700 (PDT)
Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0PUD00D00WFVXS00@nwk-mmpp-sz12.apple.com>; Tue, 09 Jul 2019 09:57:36 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 02d63d4ac31622f4425b5159c2960928
X-Va-E-CD: 25aebe0f2aa2f773f36b7efec69387bc
X-Va-R-CD: 7595d1efbde624355b8595636b1b0840
X-Va-CD: 0
X-Va-ID: c6ed8799-8c7c-4a48-a222-0082ea52f1bd
X-V-A:
X-V-T-CD: 02d63d4ac31622f4425b5159c2960928
X-V-E-CD: 25aebe0f2aa2f773f36b7efec69387bc
X-V-R-CD: 7595d1efbde624355b8595636b1b0840
X-V-CD: 0
X-V-ID: fa4c65c8-348b-442c-a021-d5b01f03795a
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-07-09_06:,, signatures=0
Received: from [17.234.23.27] (unknown [17.234.23.27]) by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0PUD00B4DWD1QW20@nwk-mmpp-sz12.apple.com>; Tue, 09 Jul 2019 09:55:50 -0700 (PDT)
Sender: rpantos@apple.com
From: Roger Pantos <rpantos@apple.com>
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3566\))
Date: Tue, 09 Jul 2019 09:55:47 -0700
Message-id: <63CAE7E1-34E9-42DA-A7DD-1E17223032AE@apple.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
X-Mailer: Apple Mail (2.3566)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-09_06:, , signatures=0
Received-SPF: pass client-ip=17.151.62.68; envelope-from=rpantos@apple.com; helo=nwk-aaemail-lapp03.apple.com
X-W3C-Hub-Spam-Status: No, score=-4.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1hktRF-0005Le-Os 29938940f1467f9c52494454f7fa63c9
X-caa-id: 11bf309c1d
X-Original-To: ietf-http-wg@w3.org
Subject: Specifying Range in Link preload header for HTTP/2 Push?
Archived-At: <https://www.w3.org/mid/63CAE7E1-34E9-42DA-A7DD-1E17223032AE@apple.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36774
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>

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


thanks,

Roger Pantos
Apple Inc.