No need to be pedantic. Yes it's the job of inetd. Inetd comes with the TCP/IP stack.
Huh, I am not pedantid, and no...
- an inetd doesn't always come with a TCP/IP stack, and when they do, they are very much optional
- they are most often not activated since that is considered a security risk.
- most inet daemons are stand alone and not directly associated with a TCP/IP stack, rinetd, xinetd, systemd socket - even on Amiga you can chose.
It's called a stack, because it consists of multiple bits of interdependent software
No, that is not why it is called a stack, you just made that up now.
and not just because the ISO OSI model is a 'stack'. But you already know that.
TCP/IP has little to do with the OSI model... TCP/IP specifically doesn't follow the OSI model - the TCP/IP stack is different from the OSI stack.
But you already know that.