On Wed, 16 Oct 2002, JINMEI Tatuya / [ISO-2022-JP] 神明達哉 wrote: > IMO, it is not necessarily a problem that nobody bothered. I've not > bothered (though I've made some comments on the draft) about the > complexity because I didn't think it was a problem of the document > based on my experiences on implementing and operating with the > specification.
It surely isn't a problem that John Doe Network User is likely to face, I agree -- the algorithm is not _that_ complex. > Please let me explain my own environments. My laptop usually has > quite a large number of addresses, and the property of the addresses > varies much; it has 12 (unicast) addresses as of writing this, > including the loopback, link-local, site-local, and global ones. It > also has temporary addresses for privacy extension, and some of the > temporary addresses are often deprecated due to the short lifetimes. > (note: the number "12" will be much increased in a few days. I > rebooted my laptop last night, so it has only one temporary address > for each autoconfigured prefix. More and more new temporary addresses > will come.) > > A few days ago, I checked statistics on the source address selection > on the laptop. By then it had been running for 6.5 days. According > to the statistics, about 76.8% of the pair-wise address comparisons > had been broken by the rule 2 (Prefer appropriate scope) and the rule > 3 (Avoid deprecated addresses). IMO, the rules 1-3 are quite simple > and light, and do not affect the performance much. The problems are likely to be seen with high use of UDP/ICMP, e.g. sending a Gigabit/FastEthernet full of UDP and checking how much that affects performance. > As a result, I don't think it is necessary to require (either SHOULD > or MUST) caching in the address selection draft. I don't oppose to > mentioning the fact that caching may improve the performance, though. I don't think we should require anything: if an implementation wants to do it the simple way, that's fine. But I believe there should be some more statements in the Implementation Considerations section, at least. -- 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] --------------------------------------------------------------------
