Re: [Idr] Fwd: I-D Action:draft-keyur-bgp-enhanced-route-refresh-00.txt

 Hi Enke, All:

As a supplement to the third question in the previous mail:

From secion 3-Operation
   "In the case of continuous churn of the BGP table, an implementation
   SHALL impose an upper bound on how long it would take to complete the
   route refresh.  Once the upper bound is reached, the implementation
   SHOULD suspend the processing of the received UPDATE messages briefly
   until the route refresh to the peer is complete."

According to my understanding of this issue, should it be not "Once" but "Before"? 
That is "the implementation SHOULD suspend the processing of the received UPDATE messages briefly
until the route refresh to the peer is complete or the upper bound is reached".

Best Regards!
Qing

----- 原始邮件 ----- 
发件人: "Qing Zeng" <zengqing@huawei.com>
收件人: "Enke Chen" <enkechen@cisco.com>; <idr@ietf.org>
抄送: "Keyur Patel" <keyupate@cisco.com>
发送时间: 2010年10月9日 16:03
主题: Re: [Idr] Fwd: I-D Action:draft-keyur-bgp-enhanced-route-refresh-00.txt

> Hi All:
> 
> I have some questions:
> 1. This is the method to checking for possible missing withdraws between BGP speakers, 
> what's the most likely to occur application scenario of  possible missing withdraws?  
> 
> 2. Why don't consider that using End-of-RIB(EOR) or extension-UPDATE message to 
> mark the beginning and the ending of a route refresh? After all, the EOR is more often
> used to mark completion of the whole Rib update for routing convergence.
> 
> 3. How to operate when BGP speaker is sending Adj-Rib-Out due to refresh with route oscillation?
> For correctly identifing the beginning and the ending of a route refresh , should route selection be hold on the speaker?
> 
> Best Regards!
> Qing
> 
> 
> 
> 
> ----- 原始邮件 ----- 
> 发件人: "Enke Chen" <enkechen@cisco.com>
> 收件人: <idr@ietf.org>
> 抄送: "Keyur Patel" <keyupate@cisco.com>
> 发送时间: 2010年10月7日 2:42
> 主题: [Idr] Fwd: I-D Action:draft-keyur-bgp-enhanced-route-refresh-00.txt
> 
> 
>> FYI.  Will appreciate comments.
>> 
>> -- Enke
>> 
>> -------- Original Message --------
>> Subject: I-D Action:draft-keyur-bgp-enhanced-route-refresh-00.txt
>> Date: Tue, 5 Oct 2010 22:00:02 -0700 (PDT)
>> From: Internet-Drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>> 
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> 
>> Title           : Enhanced Route Refresh Capability for BGP-4
>> Author(s)       : K. Patel, et al.
>> Filename        : draft-keyur-bgp-enhanced-route-refresh-00.txt
>> Pages           : 6
>> Date            : 2010-10-05
>> 
>> In this document we enhance the existing BGP route refresh mechanisms
>> to provide for the demarcation of the beginning and the ending of a
>> route refresh.  The enhancement can be used to facilitate on-line,
>> non-disruptive consistency validations of BGP routing updates.
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-keyur-bgp-enhanced-route-refresh-00.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>> 
>> 
>>
> 
> 
> --------------------------------------------------------------------------------
> 
> 
>> _______________________________________________
>> Idr mailing list
>> Idr@ietf.org
>> https://www.ietf.org/mailman/listinfo/idr
>>