Return-Path: william@bourbon.usc.edu
Delivery-Date: Fri Oct 24 15:30:00 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 m9OMU0xt009087
	for <cs551@merlot.usc.edu>; Fri, 24 Oct 2008 15:30:00 -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 m9OMeEZP021769
	for <cs551@merlot>; Fri, 24 Oct 2008 15:40:14 -0700
Message-Id: <200810242240.m9OMeEZP021769@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: cs551- final1- status msg
Date: Fri, 24 Oct 2008 15:40:14 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > How does the status msg works ? Do we have to enter at the commandline of
  > any node 'status' to get the status responses from all its neighbors ?

Correct.

  > So after entering 'status' the node should flood a status request msg with a
  > given TTL(where to get this TTL value from- is this the one in the startup
  > config file or the default TTL) with the status type set to (0x01 for
  > part1).

Please use the TTL the user entered.

  > Then how long will it have to wait for all the status responses and
  > what is to be done after getting all the status responses?

Please see:

    http://merlot.usc.edu/cs551-f08/projects/final-faq.html#done-status
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>