please, please, people, take a look at the ietf taps (“transport services”) working group :-)
Sent from my iPhone > On 3 Apr 2018, at 14:35, Mikael Abrahamsson <[email protected]> wrote: > >> On Tue, 3 Apr 2018, Jonathan Morton wrote: >> >> notwithstanding). In the end, people have kept reinventing "reliable >> datagram" protocols on top of UDP, whenever they ran up against requirements >> that TCP didn't fulfil. > > Yes, for multiple reasons. TCP is ossified and typically lives in the OS, > because of NAT the only options for protocols that work are TCP and UDP, so > if you want to move your "transmission stack" to userspace, your only choice > is UDP. So enter things like QUIC and others that are mux:ed stream protocols > over UDP, which can then live in userland on all major operating systems. > > This is not ideal, but it's not strange that this is happening. The only way > to innovate as an application/protocol developer is to use UDP. > > -- > Mikael Abrahamsson email: [email protected] > _______________________________________________ > Bloat mailing list > [email protected] > https://lists.bufferbloat.net/listinfo/bloat _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
