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

Qing Zeng <zengqing@huawei.com> Sat, 09 October 2010 08:02 UTC

Return-Path: <zengqing@huawei.com>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3FA93A682E for <idr@core3.amsl.com>; Sat, 9 Oct 2010 01:02:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.689
X-Spam-Level:
X-Spam-Status: No, score=0.689 tagged_above=-999 required=5 tests=[AWL=1.184, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQwTYm9XESDr for <idr@core3.amsl.com>; Sat, 9 Oct 2010 01:02:42 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id D2BFA3A6819 for <idr@ietf.org>; Sat, 9 Oct 2010 01:02:41 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA00047IJQ18J@szxga03-in.huawei.com> for idr@ietf.org; Sat, 09 Oct 2010 16:03:37 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA0006ZPJQ1X9@szxga03-in.huawei.com> for idr@ietf.org; Sat, 09 Oct 2010 16:03:37 +0800 (CST)
Received: from z00129659 ([10.110.98.98]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LA0003D8JQ0UG@szxml04-in.huawei.com> for idr@ietf.org; Sat, 09 Oct 2010 16:03:37 +0800 (CST)
Date: Sat, 09 Oct 2010 16:03:33 +0800
From: Qing Zeng <zengqing@huawei.com>
To: Enke Chen <enkechen@cisco.com>, idr@ietf.org
Message-id: <056d01cb6788$7808d8d0$01010164@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: base64
X-Priority: 3
X-MSMail-priority: Normal
References: <4CACC32A.7090401@cisco.com>
Cc: Keyur Patel <keyupate@cisco.com>
Subject: Re: [Idr] Fwd: I-D Action:draft-keyur-bgp-enhanced-route-refresh-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Oct 2010 08:02:43 -0000

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
>