Note on P2P HTTP re: VC HTTP API specification structure

Note that is a small P2P extension to HTTP/2 proposal

  https://tools.ietf.org/html/draft-benfield-http2-p2p-02

which allows the roles of client and server to be switched on
the same connection.

I wrote up some more links to this here, and I think it could
be very valuable to Credentials over HTTP

  https://github.com/w3c/architecture/issues/14

Henry

> On 5. May 2021, at 05:40, Manu Sporny <msporny@digitalbazaar.com> wrote:
> 
>> 
>> Keep in mind, that I am fundamentally skeptical of how we got to the
>> "current client-server" situation because the SVIP goals are so
>> extreme in asymmetry.
> 
> We got to the whole "client-server" situation because that's how HTTP
> works. It is a protocol between clients and servers, as defined in the
> HTTP specification:
> 
> https://tools.ietf.org/html/rfc7230#section-2.1
> 
> It has nothing to do with SVIP goals, power dynamics, sovereignty, or
> anything else at the political layer.
> 
>> Does HTTP require us to adopt a client-server model?
> 
> Yes, it does... and I expect your definition of "client" and "server"
> deviates from the definition in the HTTP specification. It is the
> definition in the HTTP specification that I'm using... to paraphrase:
> 
> System A (client) sends a message to System B (server).
> 
> That's it.
> 
> System A (client) could be my phone and System B (server) could be your
> phone. Note that in this case, we're talking about a peer-to-peer
> network, where we're operating as equals, and both of us have
> sovereignty (to the degree that we find acceptable) over our software
> and devices.