[ih] Why did DCCP fail to gain traction?

[John Levine]

It appears that Jack Haverty via Internet-history <jack at 3kitty.org> said:
>The question for the research community was "How do you build a 
>multi-vendor global communications system that can evolve with new 
>protocols, algorithms, and techniques, and removal of the old technology 
>that are to be replaced?"

Dunno about removal of the old stuff but QUIC is a good example of how
protocols evolve. HTTP version 1 and 2 ran over TCP, http/3 runs over
QUIC which is built on UDP so it doesn't need kernel support, with all
the multiplexing and flow control in the application. They added a new
HTTPS DNS record that browsers can query to see if a site has http/3
support. Wikipedia says that Chrome, Edge, Firefox, and Safari have
all supported http/3 and QUIC for several years, and about 40% of
Google's and Facebook's web traffic now runs over QUIC.

The popular open source web server NGINX has QUIC support, which it appears
you can enable with a one or two line configuration change.

I don't think the earlier versions of http will ever go away, but given
that a megabyte is a rounding error in application code sizes these days
I don't see that as much of a problem.

R's,
John