Thanks for the details, Mike. I read TCP/IP as TCP over IP, because TCP can be used with any data link layer that doesn't guarantee delivery.
OTOH, the first book I read about the Internet protocols was titled "TCP/IP" so there is a tendency to lump then together. I've read that the developers of IP were going to stop at the data link layer, and then decided that it wasn't a good idea to let each user develop their own scheme for verifying message delivery. TCP introduced ports so that one IP address could have 64000 sub-addresses. UDP, while not verified, does use ports. Then there all of those other application layer protocols designed to work with IP, such as ARP, DHCP, NTP, SNMP, and SNTP. Each has one or more of the 256 ports reserved for use with IP by the designers. Mills chose port 123, probably because it suited his sense of humor. Bill Hawkins -----Original Message----- From: Mike S Sent: Tuesday, February 12, 2013 1:20 PM On 2/10/2013 6:04 PM, Magnus Danielson wrote: > You should read "TCP/IP" as "Internet Protocols" (notice plural form > here). It points to the stack of protocols, Actually, no. IP is Internet Protocol, singular, and is the L3 (mostly - IP predates the ISO/OSI model layers, so IP suite protocols don't map exactly) protocol upon which both TCP and UDP are built. It's defined by RFC 791. TCP/IP, simply because those are the most commonly used protocols in the suite. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
