[Idr] draft-keyur-bgp-enhanced-route-refresh-00.xt
<stephane.litkowski@orange-ftgroup.com> Fri, 12 November 2010 11:32 UTC
Return-Path: <stephane.litkowski@orange-ftgroup.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 8BDBE3A69A3 for <idr@core3.amsl.com>; Fri, 12 Nov 2010 03:32:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.022
X-Spam-Level:
X-Spam-Status: No, score=-0.022 tagged_above=-999 required=5 tests=[AWL=2.225, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
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 pCzghja0tGIJ for <idr@core3.amsl.com>; Fri, 12 Nov 2010 03:32:33 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by core3.amsl.com (Postfix) with ESMTP id 637CB3A6944 for <idr@ietf.org>; Fri, 12 Nov 2010 03:32:33 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id 1C8861B8228 for <idr@ietf.org>; Fri, 12 Nov 2010 12:33:05 +0100 (CET)
Received: from PUEXCC51.nanterre.francetelecom.fr (unknown [10.168.74.61]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 03D82C8065 for <idr@ietf.org>; Fri, 12 Nov 2010 12:33:05 +0100 (CET)
Received: from PUEXCBL0.nanterre.francetelecom.fr ([10.168.74.46]) by PUEXCC51.nanterre.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Nov 2010 12:33:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB825D.5C9EB688"
Date: Fri, 12 Nov 2010 12:33:00 +0100
Message-ID: <6321_1289561585_4CDD25F1_6321_1504_1_4FC3556A36EE3646A09DAA60429F5335056A9663@PUEXCBL0.nanterre.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-keyur-bgp-enhanced-route-refresh-00.xt
Thread-Index: AcuCXVxnuuhf5y81QU2Wa3cLnYOQlw==
From: stephane.litkowski@orange-ftgroup.com
To: idr@ietf.org
X-OriginalArrivalTime: 12 Nov 2010 11:33:05.0372 (UTC) FILETIME=[5F5D71C0:01CB825D]
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.10.18.132415
Subject: [Idr] draft-keyur-bgp-enhanced-route-refresh-00.xt
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: Fri, 12 Nov 2010 11:32:34 -0000
Keyur, I have a major question regarding your proposal. My question is concerning the processing in parallel of transient updates and route-refresh RIB out advertisement. Consider a BGP speaker that is receiving transient updates from some peers and that will serve a route-refresh to another peer. It's very impacting to wait for the route-refresh service to be finished before sending transient updates to the peer receiving the route-refresh as it may impact customer convergence time if the RIB-OUT is huge (hundreds of thousands of prefixes). For example, a new update advertising a customer backup route to be used will be delayed to that peer. Can you confirm that in your proposal, the BGP speaker serving the route-refresh will wait to for RIB-out advertisement to be finished, then send demarcation end, finally will serve transient updates ? Thanks Stephane ********************************* This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ********************************
- [Idr] draft-keyur-bgp-enhanced-route-refresh-00.xt stephane.litkowski
- Re: [Idr] draft-keyur-bgp-enhanced-route-refresh-… Keyur Patel
- Re: [Idr] draft-keyur-bgp-enhanced-route-refresh-… altonlo