IETF Logo Mail Archive

Re: Update to OSPF Hello procedure[draft-kou-ospf-immediately-replying-hello-00.txt]

Paul Jakma <paul@CLUBI.IE> Wed, 04 January 2006 19:38 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuETE-0004Q6-5J for ospf-archive@megatron.ietf.org; Wed, 04 Jan 2006 14:38:52 -0500
Received: from wildebeest.ease.lsoft.com (wildebeest.ease.lsoft.com [209.119.0.21]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15374 for <ospf-archive@LISTS.IETF.ORG>; Wed, 4 Jan 2006 14:37:36 -0500 (EST)
Received: from PEACH.EASE.LSOFT.COM (lists.state.gov) by wildebeest.ease.lsoft.com (LSMTP for Windows NT v1.1b) with SMTP id <4.00008859@wildebeest.ease.lsoft.com>; Wed, 4 Jan 2006 14:38:21 -0500
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 95465121 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 4 Jan 2006 14:38:21 -0500
Received: from 212.17.55.49 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Wed, 4 Jan 2006 14:38:16 -0500
Received: from sheen.jakma.org (IDENT:U2FsdGVkX1/iTyVHTr/zNipJEXOoy2e3kL4172Kx6lw@sheen.jakma.org [212.17.55.53]) by hibernia.jakma.org (8.13.1/8.13.1) with ESMTP id k04Jbn0s026249 for <OSPF@peach.ease.lsoft.com>; Wed, 4 Jan 2006 19:38:00 GMT
X-X-Sender: paul@sheen.jakma.org
References: <017201c60c1e$8f545a20$610c6f0a@china.huawei.com> <Pine.LNX.4.63.0512311434400.11084@sheen.jakma.org> <000d01c610d2$61a11100$610c6f0a@china.huawei.com>
Mail-Copies-To: paul@hibernia.jakma.org
Mail-Followup-To: paul@hibernia.jakma.org
X-NSA: al aqsar jihad musharef jet-A1 avgas ammonium qran inshallah allah al-akbar martyr iraq saddam hammas hisballah rabin ayatollah korea vietnam revolt mustard gas british airways washington peroxide cool
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 15:08:11 2006 on hibernia.jakma.org
X-Virus-Status: Clean
Message-ID: <Pine.LNX.4.63.0601041924290.3405@sheen.jakma.org>
Date: Wed, 04 Jan 2006 19:37:49 +0000
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Paul Jakma <paul@CLUBI.IE>
Subject: Re: Update to OSPF Hello procedure[draft-kou-ospf-immediately-replying-hello-00.txt]
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <000d01c610d2$61a11100$610c6f0a@china.huawei.com>
Precedence: list
List-Help: <http://peach.ease.lsoft.com/scripts/wa.exe?LIST=OSPF>, <mailto:LISTSERV@PEACH.EASE.LSOFT.COM?body=INFO+OSPF>
List-Unsubscribe: <mailto:OSPF-unsubscribe-request@PEACH.EASE.LSOFT.COM>
List-Subscribe: <mailto:OSPF-subscribe-request@PEACH.EASE.LSOFT.COM>
List-Owner: <mailto:OSPF-request@PEACH.EASE.LSOFT.COM>
List-Archive: <http://peach.ease.lsoft.com/scripts/wa.exe?LIST=OSPF>

On Wed, 4 Jan 2006, Zengjie Kou wrote:

>> /independent/ of the Hello-Interval timer? (ie dont set or reset 
>> the interface's Hello timer because of any Immediate Hello sent). 
>> Otherwise, there'll be strong tendency for the HelloInterval 
>> timers across routers to latch. Not sure how much this matters.

> Yes, Immediate Hello is independent of HelloInterval timer.
> It is in favor of compatibility.

Ok, should the draft then explicitely note that Immediate-Hello 
ideally should not affect (e.g. reset) any hello timer? (so as to 
avoid the timed-interval hello synchronising).

> If Immediate Hello is multicast, all routers attached the ospf 
> networks will handle all Immediate hellos,which consumes lots of 
> cost. So, unicast is an appropriate mechanism which finishes all in 
> the peer of sending hello.

It will have a higher cost though.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
"Well hello there Charlie Brown, you blockhead."
-- Lucy Van Pelt

v2.23.0 | Report a Bug | By Email