[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RRG] Re: Does every host need a FQDN name in the future?//re:[RRG] draft-rja-ilnp-intro-01.txt
On 8/7/08 1:32 PM, Iljitsch van Beijnum allegedly wrote:
If you find yourself in the situation where the currently known
locator(s) are unreachable, you can't ask the other side for locators.
If you also can't look them up, you can't contact the correspondent
through another locator and the session is dead or can't be established.
With mobility this is especially likely as a mobile host will often not
know its new locator before the old one stops working.
In theory a locator->locator lookup would be possible, maybe through the
DNS. In that case, the ID value is superfluous.
Maybe we should simply deprecate identifiers. After all, I know who I am
and you know who you are, and the packets get there through the
locators. And if identity is really necessary, higher layers can manage
it (TLS etc).
You can't deprecate identifiers in general. We need identifiers for
mobility and for multipath transport. They don't need to be permanent,
and they can be exchanged after initial contact is established, but they
do need to be unique and stable for the duration of a session,
independent of anything that might change with topological location.
On 8/10/08 7:23 PM, Brian E Carpenter allegedly wrote:
No ;-) needed, I think. An identifier needs to be unique for as long as
it needs to be unique for. If we stipulate that no transport connection
has a lifetime greater than T, then the transport ID only needs
to be unique for T+epsilon.
Except that sessions overlap, so if it's a system-wide identifier it has
to persist until the next reboot (because new sessions will keep picking
it up and using it before previous sessions are done with it). If it's
only a session-level identifier it can be more evanescent. This would
make the multipath design more interesting.
to unsubscribe send a message to email@example.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg