The ndn6 network, my own global scale Named Data Networking network, came back earlier this year. I moved my NDNts video streaming app into the ndn6 network, to reduce dependency on the NDN testbed. How well is it performing?
QUIC ⇒ HTTP/3
In my last article "NDN video streaming over QUIC", I used Chrome browser's experimental
QuicTransport feature to perform video streaming over Named Data Networking.
The analysis revealed that QUIC transport was generally performing better than WebSockets in this application, according to metrics including video resolution and startup latency.
Web technologies are constantly evolving.
QuicTransport was in Origin Trial status at the time, but it was discontinued as of Chrome 91.
WebTransport was introduced in its place.
The main difference is that,
WebTransport uses HTTP/3 as the underlying network protocol, while
QuicTransport uses QUIC datagrams.
Since HTTP/3 runs over QUIC, I expect no performance difference between the two.
I promptly registered for the
WebTransport Origin Trial, and updated my gateways and NDNts libraries to use the new API.