• MonkderVierte@lemmy.zip
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    9 hours ago

    The TCP landscape is now a hot mess of a multitude of assistance protocols. Maybe we’ll better start from scratch, with modern usecases in in mind and while learning from past mistakes.

    • StarDreamer@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      This is practically impossible. We have proverbially locked the keys in the room. IP/UDP/TCP are here to stay due to the prevalence of buggy/nonstandard middleboxes (hardware firewalls, ASIC switches, NAT routers) in the Internet.

      We have new protocols, new theories for networking (look at NDN, in which is physically incapable of being censored or ddosed). However, anything that doesn’t conform to existing IP/TCP/UDP will get dropped by these so-called “middleboxes”. Even things that DO conform to IP/TCP/UDP will sometimes get dropped by these middleboxes (e.g. new TCP extensions, QUIC, etc). We cannot build an Internet replacement without almost fully scrapping every piece of networking equipment deployed since the 90s.

      Middleboxes were supposed to be a temporary solution until we could transition to a new protocol like IPv6. Companies went for the cheap solution and violated the end-to-end principle of networking instead. Now we’re paying the price and stuck with it.

      • MonkderVierte@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        3 hours ago

        I mean, yeah, but most protocols (like DNS, CORS) are a patch on changed usecases or missed consideration.

    • BeigeAgenda@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      I’m sure we can vibe something in a few minutes, I’ll solve so many problems when we are forced to use smoke signals for the latest memes.