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

Zengjie Kou <kouzengjie@HUAWEI.COM> Thu, 02 March 2006 02:52 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEdvz-0000kA-RS for ospf-archive@LISTS.IETF.ORG; Wed, 01 Mar 2006 21:52:55 -0500
Received: from wildebeest.ease.lsoft.com ([209.119.0.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEdvz-0005Ln-HO for ospf-archive@LISTS.IETF.ORG; Wed, 01 Mar 2006 21:52:55 -0500
Received: from PEACH.EASE.LSOFT.COM (lists.state.gov) by wildebeest.ease.lsoft.com (LSMTP for Windows NT v1.1b) with SMTP id <5.0003AFB9@wildebeest.ease.lsoft.com>; Wed, 1 Mar 2006 21:52:54 -0500
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 100779443 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 1 Mar 2006 21:52:53 -0500
Received: from 12.129.211.51 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Wed, 1 Mar 2006 21:52:53 -0500
Received: from huawei.com ([172.24.2.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVH00E5IBIDOZ@usaga01-in.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Wed, 01 Mar 2006 18:42:14 -0800 (PST)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVH007PBC8X0F@szxga02-in.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu, 02 Mar 2006 10:58:09 +0800 (CST)
Received: from szxml02-in ([172.24.1.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVH00BMTC8RE1@szxga02-in.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu, 02 Mar 2006 10:58:09 +0800 (CST)
Received: from k49110 ([10.111.12.97]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IVH00ES9C8N98@szxml02-in.huawei.com> for OSPF@PEACH.EASE.LSOFT.COM; Thu, 02 Mar 2006 10:57:59 +0800 (CST)
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
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> <43FF13BB.9030903@cisco.com> <000801c63c19$3121b760$610c6f0a@china.huawei.com> <44044364.30701@cisco.com>
Message-ID: <001701c63da3$58fd0ba0$610c6f0a@china.huawei.com>
Date: Thu, 02 Mar 2006 10:45:20 +0800
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Zengjie Kou <kouzengjie@HUAWEI.COM>
Subject: Re: draft-kou-ospf-immediately-replying-hello-00.txt
To: OSPF@PEACH.EASE.LSOFT.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: c2e58d9873012c90703822e287241385

Hi, Acee
    Yes, you are correct.

     There are two cases as following when DR election.
 Case 1:
0----------------------------------------------------------------------------> Time
          init->2-way ----------------------- dr election
                                |
                                |
                          Sending Immediate Hello


Case 2:
0----------------------------------------------------------------------------> Time
          init->2-way ----------------------- dr election         |
                                                                  |
                                                                  |
                                                             Sending Immediate Hello

For case 2, the DR election result is same to RFC2328.
For case 1,the DR election result is different  to RFC2328.

In order to keep consistent to RFC2328, we may adopt case2 in immediate hello.

Thanks,
Zengjie


----- Original Message ----- 
From: "Acee Lindem" <acee@CISCO.COM>
To: <OSPF@PEACH.EASE.LSOFT.COM>
Sent: Tuesday, February 28, 2006 8:34 PM
Subject: Re: draft-kou-ospf-immediately-replying-hello-00.txt


> Zengjie Kou wrote:
> 
>>Hi, Acee
>>    On p2p networks, there is no distinction between first coming or coming back up. The immediate hello is efficient in discover neighbors and convergence.
>>    On broadcast networks, when an interface first coming, DR election need to wait  wait-time. However, when an interface coming back up, DR election need not to wait wait-time(if BDR exists or the down interface is not DR). Here, only HelloInterval or     BackupSeen is needed to discover neighbor or convergence. Immediate hello avoids the HelloInterval or backupSeen on the case.
>>  
>>
> Hi Zengjie,
> 
> I think you're saying the hello when the DR/BDR interface state changes 
> is solely for
> the case when the BDR's interface flaps. Correct?
> 
>     BDR Interface goes down
>     Ex-BDR Interface comes back up
>     Ex-BDR send initial hello ----------------------------> Other 
> Routers on LAN
>     Ex-BDR goes to 2-way <----------------------------   Other Routers 
> Immediate reply
>                                                                                          
> New DR/BDR election
>     Triggers election on  Ex-BDR  <----------------------   New DR/BDR 
> send hello
> 
> Why not just process the neighbor change event before sending the 
> immediate reply?
> In other words, perform the new DR/BDR election before the immediate 
> reply hello?
>                   
> Thanks,
> Acee
> 
>>Thanks,
>>Zengjie
>> 
>> 
>>----- Original Message ----- 
>>From: "Acee Lindem" <acee@CISCO.COM>
>>To: <OSPF@PEACH.EASE.LSOFT.COM>
>>Sent: Friday, February 24, 2006 10:10 PM
>>Subject: Re: draft-kou-ospf-immediately-replying-hello-00.txt
>>
>>
>>  
>>
>>>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
>>>>>>>>> 
>>>>>>>>>
>>>>>>>>>      
>>>>>>>>>
>>>>>>>>>           
>>>>>>>>>
>>>>>>>>>                
>>>>>>>>>
>>>>>>>>    
>>>>>>>>
>>>>>>>>         
>>>>>>>>
>>>>>>>>              
>>>>>>>>
>>>>>>     
>>>>>>
>>>>>>          
>>>>>>
>>>> 
>>>>
>>>>      
>>>>
>>
>>  
>>