Re: Site local

[Iljitsch van Beijnum <iljitsch@muada.com>]

On Fri, 6 Dec 2002, Kurt Erik Lindqvist wrote:

> > In a identifier/locator system, the endpoints are always aware of the
> > identifiers. Since such a system isn't here yet, we can make this a  very
> > hard requirement. Changing the locators around is then no longer an issue.

> I am still worried about some of the application protocols, but I am
> not a applications guy. So I still think we should get this run through
> the applications area.

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
important information here is the destination address/name and port, but
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.

All reasonably simple. The problems start when one or both ends (or a
third and so on end) of the communication puts information about the
addresses and ports in a protocol but these addresses/ports aren't the
ones aren't the real ones because they are changed somewhere along the
way.

If we create new identifiers for the applications to work with and make
sure those aren't changed in the middle at any point, we should be fine.

Iljitsch