Yes and no. TCP is a transport protocol that sits on top of IP. All of the specifications are public domain RFCs. TCP just needs a network layer to function. IP is the modern network layer (layer 3) that all routers use to communicate. I have very little experience with this layer, but I do believe routing equipment would be mostly "hard-coded" to use the IP protocol.
That being said a modern networking stack is usually built directly into the hardware. Intel and Broadcom networking controllers defer TCP to the controller itself rather than the OS or even driver code. This is called TCP offloading. Most (if not all) offloading code would run locally to the network controller and likely closed source.
In embedded applications, source code usually needs to be available to the system building it but often have proprietary licensing.
Here is the Linux IPV4 stack source code if you are so inclined.
https://github.com/torvalds/linux/tree/master/net/ipv4
To further your point, unless we move networking into user-space which is a very dumb idea for many reasons imo, we will need to "rely" on proprietary IP hardware stacks if we want performance. As far as DNS goes, yeah that's actually centralized and "controlled" by the state. However I believe we should do whatever bitcoin does. TMK bitcoin primarily relies on DNS for node discovery and some basic security.
If anyone sees this and wants to contribute to open hardware and operating systems the Redbean project could use your help I'm sure, I could get you in touch!
ChipTuner
npub1qd…3fqm7
2024-04-02 19:42:04
in reply to nevent1q…xdqg
Author Public Key
npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7Published at
2024-04-02 19:42:04Event JSON
{
"id": "e9932438e7eb6c2bd38bb11c235bcbbe07bc611198f608e5edbd5ecbc87ad8fb",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1712086924,
"kind": 1,
"tags": [
[
"e",
"6647af09d695d41edf3ef83124b0e65b923438b016089883815935cb52e1ea9c",
"",
"root"
],
[
"e",
"21f068b2f550532ca040bbab7ba5601c651c1e9d7353a2dcd5b44d734c1709eb",
"",
"reply"
],
[
"p",
"f821179bd5d691c61b4356336388adadc3cc1304f49e771a87c38de7ed4fd022"
],
[
"p",
"53a91e3a64d1f658e983ac1e4f9e0c697f8f33e01d8debe439f4c1a92113f592"
]
],
"content": "Yes and no. TCP is a transport protocol that sits on top of IP. All of the specifications are public domain RFCs. TCP just needs a network layer to function. IP is the modern network layer (layer 3) that all routers use to communicate. I have very little experience with this layer, but I do believe routing equipment would be mostly \"hard-coded\" to use the IP protocol. \n\nThat being said a modern networking stack is usually built directly into the hardware. Intel and Broadcom networking controllers defer TCP to the controller itself rather than the OS or even driver code. This is called TCP offloading. Most (if not all) offloading code would run locally to the network controller and likely closed source. \n\nIn embedded applications, source code usually needs to be available to the system building it but often have proprietary licensing. \n\nHere is the Linux IPV4 stack source code if you are so inclined.\nhttps://github.com/torvalds/linux/tree/master/net/ipv4\n\nTo further your point, unless we move networking into user-space which is a very dumb idea for many reasons imo, we will need to \"rely\" on proprietary IP hardware stacks if we want performance. As far as DNS goes, yeah that's actually centralized and \"controlled\" by the state. However I believe we should do whatever bitcoin does. TMK bitcoin primarily relies on DNS for node discovery and some basic security. \n\nIf anyone sees this and wants to contribute to open hardware and operating systems the Redbean project could use your help I'm sure, I could get you in touch!",
"sig": "d3a7b500388e00624584ad770989ec63f2b885277f23a917cd6a7ca23954ecb3fc52c8ad8292f3f464f788a42f192e2d36963f819f2f805827fbb0b9370d0922"
}