On Mon, 24 Sep 2001, Richard Draves wrote:
> But putting that aside: I would argue that SA is the better choice,
> because I think choosing a correctly-scoped source address is more
> important than avoiding deprecated addresses. If SB is chosen, then when
> D goes to reply to SB, communication might be prevented because of the
> scope mismatch. Whereas if SA is chosen, then communication will succeed
> until such time as SA expires (if it expires). D, and all the routers in
> between, don't know that SA is deprecated. But scope mismatches can
> cause problems. (Eg in the past some implementations have refused to
> communicate with mismatched scope, or depending on routing vagaries
> communication from D to SB could result in a scope-exceeded ICMP error.)
Am I missing something here, or are we changing the definition/expected
use of 'deprecated address' here? Previously, I think, it was very
clearly not to be used as a source address, to be phased out when
connections using it die off.
If we start re-using 'deprecated address' for new connections under
certain scenarios, we may never actually manage to get rid of it.
After all, deprecated usually _should_ be either refreshed or removed.
If we keep using it anyway, _when_ it is absolutely removed, we're going
to have bigger problems anyway.
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
