Wow, that's incredible.
>Port number themselves stem from TCP emerging from earlier protocols (see the
>early RFCs 322, 349, 433 and those that obsolete them), and a clean design
>would probably elect to eschew them, leveraging a \(2^{128}\) address space to
>allow process-to-process communication, instead of the route-to-host, then
>route-to-process dance we do know.
>
>The host to process frontier should be an implementation detail on the
>receiving end, not baked so deeply in the stack.
>This barrier may even change from request to request as new hosts come up or
>down depending on load.
>This already happens anyway with e.g. kubernetes, but we would have less cruft
>if it was baked into the protocol.
That sounds like some of the problems RINA was trying to solve.
https://en.wikipedia.org/wiki/Recursive_Internetwork_Architecture
