Re: identity persistence and comparison issues

Brian E Carpenter wrote:

> Iljitsch van Beijnum wrote:
> 
...
>> In other words, the bind(2) call can trigger the creation of a 
>> longer-lived identifier. Still, I'm not sure how applications 
>> determine which address to use in referrals, it may be necessary to 
>> make this an explicit API call = application changes = a bad thing.
> 
> 
> That's an interesting point. In a 2-way conversation, a 'close' on a socket
> is a strong signal that the stack can forget any state (unless there is
> some optimization possible by caching the state)....

'close' is an app-side input to the stack; there are other 
considerations about when to drop state.

E.g., TCP has to keep TIME_WAIT to avoid reusing ports/seq numbers. At 
which point addresses from elsewhere cannot be moved 'here' until these 
timers expire.

Joe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA2vQaE5f5cImnZrsRAu7LAJ9Tx/WfpN+KWYM4n5QYYJssSr0j5gCg50GG
Oz/uo80Rfa24w2JfpOmTq5U=
=hpt4
-----END PGP SIGNATURE-----