HTTP2 server-side stream creation

[Ben Maurer <[e-mail]>]

I've currently been looking at framing protocols that are appropriate to
use in a peer to peer context where there is less of a distinction between
client and server.

This 4-year-old thread (which I selected an email in the middle of, that
best represents the core of the question) discusses this type of approach.

https://lists.w3.org/Archives/Public/ietf-http-wg/2015JulSep/0043.html

Even though the spec says that "Clients send HTTP requests and receive HTTP
responses" it also states that "Streams initiated by a client MUST use
odd-numbered stream identifiers; those initiated by the server MUST use
even-numbered stream identifiers". This implies that servers can in fact
receive some sort of request and provide a response.

The thread seems to conclude that it's at least plausible to use HTTP2 in
this context.

I attempted to find conversations since that time and couldn't find any.
I'm curious if people are aware of any attempts to take this approach.

As a more concrete example, imagine one were creating a protocol like
bittorrent (where both peers of a connection may initiate requests) would
HTTP2 be an appropriate base layer for that protocol (allowing either peer
to initiate a request a chunk of data in the case of bittorrent).

-b