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

[Roger Pantos <[e-mail]>]

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.