Return-Path: william@bourbon.usc.edu Delivery-Date: Wed Oct 15 10:16:47 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m9FHGlAo005173 for ; Wed, 15 Oct 2008 10:16:47 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m9FHOkK5003536 for ; Wed, 15 Oct 2008 10:24:46 -0700 Message-Id: <200810151724.m9FHOkK5003536@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Waiting for Join Response Date: Wed, 15 Oct 2008 10:24:46 -0700 From: Bill Cheng Someone wrote: > When a non-beacon node comes up, it sends Join Request to any one of the > Beacon Node. > Now this beacon node will flood this Join message to all its neighbors. > But how long should the requesting non-beacon node wait for the response > since it is not aware of number of nodes in the network and also has no idea > of the network condition. If you really want to use a timeout, you can use a small multiple (say 1.1) of MsgLifetime since after MsgLifetime, other nodes in the network will not forward responses for the JOIN request message in question. -- Bill Cheng // bill.cheng@usc.edu