NDN over WebSockets == TCP over TCP
Named Data Networking (NDN) was first ported to web browser environment in 2012.
Feeling that WebSocket is a better match for the NDN implementation at the time, I wrote the initial code for a CCNx WebSocket proxy.
Web applications would connect to this proxy over TCP, negotiate a WebSocket connection, and send NDN packets in WebSocket frames.
The proxy then decapsulates these frames, and delivers the NDN packets to ccnd forwarder over TCP.
NDN-over-WebSockets survived multiple protocol changes over the years, and made its way into the NDN Forwarding Daemon (NFD).
It worked fine for simple NDN web applications, such as status pages and text chat, and even file retrievals.
Recently, with the rise of video streaming on the NDN testbed, congestion control functionality starts to show up in NDN libraries.
Then, a question popped into my mind: WebSockets run over TCP, and NDN congestion control algorithms are largely borrowed from TCP, would this cause any problems?