Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Sep 28 20:01:46 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 m8T31k0Y007356 for ; Sun, 28 Sep 2008 20:01:46 -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 m8T35jVE026149 for ; Sun, 28 Sep 2008 20:05:45 -0700 Message-Id: <200809290305.m8T35jVE026149@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: cs551 Part1 Date: Sun, 28 Sep 2008 20:05:45 -0700 From: Bill Cheng Someone wrote: > The specification says : > KeepAliveTimeout* - If a node has not seen *any* message from a neighbor > after this timeout (in seconds) has occurred, it should close its connection > to this neighbor. The default value is 60. > > The question is : > It does not mention anything regarding KeepAlive > message .Do we have to wait for KeepAliveTimeOut before sending > keepalive message or should we consider this as the time out after sending > the keep alive message and then conclude that the neighbor has gone down. It's best to send a message every KeepAliveTimeout/2 seconds, just to be safe! > Also the above spec says "any" message .Please Explain On a connection, if you see any message, you should reset your keep alive timer back to the KeepAliveTimeout value. -- Bill Cheng // bill.cheng@usc.edu