Hi Roland, On Fri, Oct 23, 2020 at 8:34 PM Roland Zink <[email protected]> wrote:
> A application works with a single connection most of the time. As > application developer you probably can't afford to put any effort in > improving this when it isn't absolute necessary. If you do it on the > application layer then the application may also get location information > out of it, like IP addresses or WiFi names, and this is a privacy issue. > This is an interesting thought and I wonder if you might be able to elaborate some. The userland QUIC libraries I'm familiar with require applications to do a lot of their own lifting with regards to the network. I'm particularly interested whether there is any difference say between: 1) An HTTP/3 client application that wants to open two QUIC connections using a userland QUIC library. 2) An HTTP/3 client application that wants to open one multipath QUIC using a userland QUIC library. Is the expectation here that there is some TBD OS-level API would abstract network layer information from the application in the name of privacy? Cheers Lucas > >
