Re: draft-kou-ospf-immediately-replying-hello-00.txt

Acee Lindem <acee@CISCO.COM> Fri, 24 February 2006 14:10 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCde6-0001B7-1V for ospf-archive@LISTS.IETF.ORG; Fri, 24 Feb 2006 09:10:10 -0500
Received: from wildebeest.ease.lsoft.com ([209.119.0.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCde5-0003wn-P8 for ospf-archive@LISTS.IETF.ORG; Fri, 24 Feb 2006 09:10:10 -0500
Received: from PEACH.EASE.LSOFT.COM (lists.state.gov) by wildebeest.ease.lsoft.com (LSMTP for Windows NT v1.1b) with SMTP id <9.0003513C@wildebeest.ease.lsoft.com>; Fri, 24 Feb 2006 9:10:09 -0500
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 100289746 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 24 Feb 2006 09:10:09 -0500
Received: from 171.71.176.71 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Fri, 24 Feb 2006 09:10:09 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 24 Feb 2006 06:10:08 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k1OEA3Hh019434 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 24 Feb 2006 06:10:04 -0800 (PST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 24 Feb 2006 09:10:04 -0500
Received: from [10.82.216.60] ([10.82.216.60]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 24 Feb 2006 09:10:04 -0500
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <43F63D76.4030009@cisco.com> <000b01c635cb$cddcca30$610c6f0a@china.huawei.com> <43F9DD10.8040305@cisco.com> <001601c636e4$5ea03980$610c6f0a@china.huawei.com> <43FCDA9B.9050307@cisco.com> <000701c63928$9908e590$610c6f0a@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Feb 2006 14:10:04.0301 (UTC) FILETIME=[022673D0:01C6394C]
Message-ID: <43FF13BB.9030903@cisco.com>
Date: Fri, 24 Feb 2006 09:10:03 -0500
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@CISCO.COM>
Subject: Re: draft-kou-ospf-immediately-replying-hello-00.txt
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <000701c63928$9908e590$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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8

Zengjie Kou wrote:

>Hi, Acee
>   The empty hello mechanism that you refered is adopted by most OSPF implementations indeed when an interface first comes up.
>I agree this. However, when an normal interface whose state is up goes down then up, immediate hello  is  effective by avoiding 
>helloInterval or backupSeen.
>  
>
Hi Zengjie,

I don't think there should be a distinction between first coming or 
coming back up.

Thanks,
Acee

>Thanks,
>Zengjie
> 
>----- Original Message ----- 
>From: "Acee Lindem" <acee@CISCO.COM>
>To: <OSPF@PEACH.EASE.LSOFT.COM>
>Sent: Thursday, February 23, 2006 5:41 AM
>Subject: Re: draft-kou-ospf-immediately-replying-hello-00.txt
>
>
>  
>
>>Zengjie Kou wrote:
>>
>>    
>>
>>>Hi, Acee,
>>>   You are right, immediate hello does not provide the mechanism of detecting link down fast. But, immediate hello improve to discover neighbors when interface goes down then up. In practice, the requirement is needed.
>>> 
>>>
>>>      
>>>
>>Hi Zengjie,
>>
>>Speaking strictly in terms of state machines, it seems the interface 
>>would lose it's DR/BDR state
>>when it goes down (and cannot send a hello). Wouldn't this scenario be 
>>better handled
>>by the empty hello many OSPF implementations send when an interface 
>>first comes up?
>>
>>Thanks,
>>Acee
>>
>>    
>>
>>>Thanks,
>>>Zengjie
>>>
>>>----- Original Message ----- 
>>>From: "Acee Lindem" <acee@CISCO.COM>
>>>To: <OSPF@PEACH.EASE.LSOFT.COM>
>>>Sent: Monday, February 20, 2006 11:15 PM
>>>Subject: Re: draft-kou-ospf-immediately-replying-hello-00.txt
>>>
>>>
>>> 
>>>
>>>      
>>>
>>>>Hi Zengjie,
>>>>
>>>>Zengjie Kou wrote:
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>Hi,Acee,
>>>>>  If a router interface whose role is changed(e.g.DR goes down), the router will notify all routers about the change by immediate hello.
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>This is only when the DR/BDR knows that it is going down or the case 
>>>>where the router
>>>>priority is set to 0.
>>>>
>>>>For a router becoming DR/BDR, all the routers should elect the same DR/BDR
>>>>so I don't see how it helps.
>>>>
>>>>Thanks,
>>>>Acee
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>After all router get the change, election will be reprocessed. In contrast to normal hello, immediate hello avoid the backupSeen.
>>>>>Namely, improving convergence.
>>>>>
>>>>>Thanks a lot,
>>>>>Zengjie
>>>>>
>>>>>----- Original Message ----- 
>>>>>From: "Acee Lindem" <acee@CISCO.COM>
>>>>>To: <OSPF@PEACH.EASE.LSOFT.COM>
>>>>>Sent: Saturday, February 18, 2006 5:17 AM
>>>>>Subject: draft-kou-ospf-immediately-replying-hello-00.txt
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>>>Hi Zengjie,
>>>>>>
>>>>>>Under what situations does having the router who changed to/from
>>>>>>DR/BDR improve convergence (section 6.2)? Since DR/BDR election
>>>>>>is a distributed algorithm dependent on the calculating routers state, it
>>>>>>seems this won't help in all that many cases.
>>>>>>
>>>>>>Thanks,
>>>>>>Acee
>>>>>>  
>>>>>>
>>>>>>       
>>>>>>
>>>>>>            
>>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>> 
>>>
>>>      
>>>
>
>  
>