Return-Path: william@bourbon.usc.edu Delivery-Date: Sat Sep 27 21:09:29 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 m8S49Tts020073 for ; Sat, 27 Sep 2008 21:09:29 -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 m8S4DDaL006931 for ; Sat, 27 Sep 2008 21:13:13 -0700 Message-Id: <200809280413.m8S4DDaL006931@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: 551 final1 Date: Sat, 27 Sep 2008 21:13:13 -0700 From: Bill Cheng Someone wrote: > After the node has sent out the JOIN request how does the node decide that > it will be receiving 'n' number of JOIN response messages. > > Does it wait for the JoinTimeOut and and assume that the the number of > responses it has got is the number of Beacon nodes are active at the time > and then proceed from there. If your network has 3 beacon nodes and 12 regular nodes and the 16th node is joining the network, it should get 15 join responses, one from each node. This 16th node does not know how many nodes there are in the network, so it must wait for JoinTimeout to expire. After JoinTimeout expires, it sorts all the join responses it got and look at the ones with the smallest distance values. -- Bill Cheng // bill.cheng@usc.edu