|
That is correct. Iroh connections are at L6, individual protocols such as blobs or gossip are at L7. From the OSI point of view, QUIC itself is a bit of a layering violation. It covers transport (L4, Reliable ordered delivery, stream multiplexing, congestion control, ...), session (L5, connection establishment and lifecycle, path migration, ...) and presentation (L6, encryption). And of course below that we have the ability to provide custom transports. This was done intentionally in QUIC to provide more control. The application layer doesn't have to care about what goes on below, but for some advanced use cases it can know what's going on and even influence which path is being used. QUIC/TLS being such a comprehensive and well tested package allows us to delegate a lot of the work and just add a tiny bit of logic to make it peer to peer. Although delegate is not exactly right, since we ended up having to write our own QUIC implementation, noq, to support QUIC multipath... |