Re: [quicwg/base-drafts] Make reset simpler and invisible (#574)

[MikkelFJ <[e-mail]>]

> I think that we need to discuss expectations about peer-to-peer operation at some point. I see a lot of requests coming in that don't at all fit with my experience of how peer-to-peer works.

I suppose you consider peer-to-peer like Skype where the client traverses NAT to a cloud infrastructure out to another client.

Peer-to-peer can also mean server to server in a distributed system, at multiple levels: same data center, different data centers, different IP address ranges etc. but common for these are that it is random who initiates the connection and both might attempt to do so at the same time. Over time two entities may switch between being client and server.

Such a setup may also involve routing messages across multiple entities using algorithms such as Kademlia and Chord. This opens up some concerns regarding end-to-end flow control over a routed network while the link level connection would be QUIC. For example, streams might be forwarded using QUICs stream flow control mechanism, and some eggs might have to be broken to achieve the end result (i.e. not fully adhering to spec).

Another similar scenerio is mesh networks for sensor networks, but there are industry adhoc standards emerging for such networks I believe. Here some nodes may be promoted to being internal routing nodes and others edge nodes, though who gets chosen for what can be fairly arbitrary and changing over time.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/574#issuecomment-306193652