tef,
@tef@mastodon.social avatar

seen a take about tcp and it's just making me come out in "well actually" and i need to vent

like, sure, tcp/ip is great, but it's worth learning about sequence numbers (syn cookies), or congestion collapse (tcp reno), or the vestigial options no-one handles correctly

we're told things like "tcp/ip was split so that ip can be simple" and then people cough and mumble out "ip fragmentation and reassembly"

tef,
@tef@mastodon.social avatar

the point i want to make is that a lot of tcp's good design is accidental, the bad parts have been fixed, mostly, and the adoption of tcp was way more about social factors than technical ones

the protocol everyone adopted wasn't the polished turd we know and love. that and tcp/ip4 has been so successful that it has effectively sabotaged efforts to replace it

it isn't so much well designed but well positioned, lucky, and malleable enough to overcome problems (of which there were many)

alarig,
@alarig@hostux.social avatar

@tef @fanf Polished, polished… could we talk how badly it handles uncommon MTU just because the MSS negotiation is only two ways instead of three ways?

wxcafe,
@wxcafe@social.wxcafe.net avatar

@tef begging devs to look at the spec for one (1) core network protocol before talking about networks from half-remembered simplifications

fanf,
@fanf@mendeddrum.org avatar

@wxcafe @tef i wonder if i should actually look at the tcp redux rfc, or just continue to enjoy the knowledge that it exists

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • DreamBathrooms
  • mdbf
  • ethstaker
  • magazineikmin
  • GTA5RPClips
  • rosin
  • thenastyranch
  • Youngstown
  • osvaldo12
  • slotface
  • khanakhh
  • kavyap
  • InstantRegret
  • Durango
  • provamag3
  • everett
  • cisconetworking
  • Leos
  • normalnudes
  • cubers
  • modclub
  • ngwrru68w68
  • tacticalgear
  • megavids
  • anitta
  • tester
  • JUstTest
  • lostlight
  • All magazines