On Tue, Aug 02, 2005 at 07:22:09PM +0900, Arifumi Matsumoto wrote: > > Additionally, > at v6ops session yesterday, 6net people showed us another > possible usage of address selection policy table. It's renumbering. > By pouring address selection policy into each end hosts, > you can easily configure address selection policy that > makes end-hosts not to use old address.
There were two 'interesting' states during the renumbering we did. 1) Both prefixes equally valid. Here the address selection was somewhat 'arbitary' on the four OSes we tested. In reality this didn't matter too much, but it might be nice to have a policy distribution method indicate a shift to prefer the new prefix before deprecating the old one. 2) Old prefix deprecated. In this case the four OSes all selected addresses correctly, i.e. preferred active over deprecated addresses. This allows the Baker process to basically work, at least for the host configuration aspect. As an aside, the undesirable property we observed after the deprecated address became invalid (removed) was that applications and tools continued to use that address as a source, but would never see replies. One assumes the address validity is only checked at bind time. But that raises the issue of how often the distributed policy is rechecked by the system or applications. Tim -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
