Tcpls: Modern Transport Services with TCP and TLS

Re:Tcpls: Modern Transport Services with TCP and TLS by stormbrew on Sunday June 05, 2022 @05:07PM (#31634874)

Most of this is just retreading the other thread so I'm largely going to just say you can read my replies there, but to explicitly reiterate:

> They had to introduce a new standardized transport if the hope was to solve the HOL blocking issue.

I take no issue with quic being standardized and I applaud that it was.

> Furthermore it all would have been pointless to define QUIC as a standard without actually applying it in practice, in anger, to real workloads.

Protocols are deployed on real workloads in anger in practice every day without even having an ietf rfc, let alone being blessed as the next official version of one of the most important protocols on the internet, and it works out fine. I never said, meant, or in any way advocated for anyone sitting on their ass.

[ Parent | on HN ]

Re:Tcpls: Modern Transport Services with TCP and TLS by aseipp on Sunday June 05, 2022 @05:12PM (#31634913)

So based on reading your other responses your complaint is that "I think RFCs are built on practice than the other way around" which doesn't mean much, considering that's what is happening! They are building on practice. Most if not all RFCs anywhere, including the IETF, actually see lots of revisions, and QUIC is hardly very different, and there is no hard rule about how standards are formed. This is how it works.

EDIT: I was too rude/curt and re-edited this. Sorry.

[ Parent | on HN ]