More to the list of situations, how would we support multicast in this model? Do we need to?Well, let's create something that we feel comfortable showing others first.
I don't think the application part is all that complex. Either you are a
sender or a receiver. The sender sets up a session or packet. The most
Well, the same goes for NAT and applications still don't work :)
important information here is the destination address/name and port, butWell, my worry is that we (I at least) don't understand all application designs well enough to make the claim that the above model would hold as a benchmark.
the sender may also specify a source. The sender fires off a TCP session
or a (UDP) packet. Meanwhile, the receiver has started listening on an
address/port. A packet or session request comes in. The receiver looks
at the source address/port and decides whether to accept the
session/packet.