this post was submitted on 23 Sep 2023
276 points (97.3% liked)
Open Source
31705 readers
221 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
TIL UDP Traffic runs on TCP.
"TCP/IP" is conventionally used to indicate the whole protocol suite; including UDP, ICMP and sometimes even ARP.
Technically the parent protocol is IP.
In all my years I have never heard someone suggest that TCP is a catch all term.
I've seen many references to TCP/IP as meaning IP + everything-on-top, usually when talking about other networking technologies like UUnet, OSI, etc. Also as the TCP/IP stack, usually meaning the (Free)BSD networking code used in other systems.
It's not that TCP is a catch-all term, but "TCP/IP" is often used that way.
https://en.wikipedia.org/wiki/Internet_protocol_suite
For that matter, the classic networking text by Douglas Comer is Internetworking with TCP/IP and it does cover UDP, ICMP, ARP, DHCP, DNS, etc.
It does it you want to be sure it is delivered!
Psh. UDP isn't used at any scale anymore. /s
I use it all the time
I use it all the time
I use it all the time
I use it all the time
Psh
Wut