3 ms·
Possibly not very on topic, but it might not be wise to call TCP a single standard when it has become to complex nowadays. The tangled mess of RFCs describing T
by kccqzy 11y ago
Possibly not very on topic, but it might not be wise to call TCP a single standard when it has become to complex nowadays. The tangled mess of RFCs describing TCP has become so complex that an RFC is written to provide a roadmap of TCP[0]. And that roadmap references more than 150 other RFCs.
[0]: https://tools.ietf.org/html/rfc7414 https://tools.ietf.org/html/rfc7414
- chetanahuja 11y agoHeh... The problem here is that TCP is being asked to do too much now. We're expecting the same protocol to work well over the entire range of networks. Starting with two servers on the same 10 gig switch with a ping latency in microseconds all the way to mobile networks with intermittent connectivity and 100's of milliseconds ping latency. The ironical outcome of all this is that devs concerned about performance now need to spend a lot of time on thinking about how to work around the problems of TCP in their particular use case. This is becoming more and more of a pain in the mobile app world because of obvious reasons.
- simoncion 11y ago> And that roadmap references more than 150 other RFCs. I count eight RFCs in the "Core Functionality" section. [0] I count ~26 RFCs in the "Strongly Encouraged Enhancements" section. [1] The remaining referenced RFCs are: * Experimental extensions to TCP * IANA guidelines to follow when one is extending TCP * Documents referenced only because of their historical significance * Documents that provide implementation insights derived from TCP implementers' war stories over the years Between eight and ~thirty-four RFCs is a damn sight smaller than "more than 150". [0] This section is stuff that must be implemented to speak TCP. [1] That section is stuff that improves the performance and/or security of TCP implementations, but is not required to interoperate with other TCP implementations.