No, TCP/IP is just a name of the suite, there's no such thing as UDP/IP, just because person who wrote the cloudflare glossary invented it doesn't mean it is an

No, TCP/IP is just a name of the suite, there's no such thing as UDP/IP, just because person who wrote the cloudflare glossary invented it doesn't mean it is an accepted term. Frankly UDP over any other protocol than IP makes very little sense, UDP header literally are just 4 fields: - source port - destination port - length of the datagram - checksum that's it, and just ports by themselves are not really useful for anything. The name TCP/IP comes because TCP and IP protocols were created together and closely coupled. Soon they were separated and other protocols were added (UDP, ICMP, IGMP, ARP and many others), but the name stayed. The TCP/IP name stands for the protocol suite, and things like UDP/IP were invented by people who didn't understand its meaning. Here are definitions from ICANN: https://icannwiki.org/TCP/IP https://icannwiki.org/TCP/IP Many other authoritative places: Bunch of RFCs (this one is from 90s): https://tools.ietf.org/html/rfc1180 https://tools.ietf.org/html/rfc1180 https://computerhistory.org/profile/vint-cerf/ https://computerhistory.org/profile/vint-cerf/ This term was used essentially from the beginning of the Internet: http://www.columbia.edu/~rh120/other/tcpdigest_paper.txt http://www.columbia.edu/~rh120/other/tcpdigest_paper.txt