On Thu, Jul 16, 2009 at 10:46 PM, Bruce Lowekamp<[email protected]> wrote: > 1) rely on the clients to periodically Ping or Route_Query to ensure > they are connected to the correct peer. Unfortunately, this leaves an > obvious gap before the topology change is noticed. Unlike > sip-outbound, we don't have redundant connections to compensate for > temporary loss of reachability. > > 2) define a new method for this purpose that is generic, so > independent of overlay algorithm > > 3) retain the current use of Update, and specify that a client > receiving an Update that it cannot process (because it does not speak > the overlay algorithm) SHOULD perform a Route_Query to confirm it is > still connected to the proper peer.
I should have been more clear that options 2 and 3 are peer-initiated (so 2 would be a new Request a peer sends to all members of its connection table when its responsible ID range changes). Bruce _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
