Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-06.txt
"Keyur Patel (keyupate)" <keyupate@cisco.com> Thu, 06 February 2014 17:51 UTC
Return-Path: <keyupate@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6D71A03EA for <idr@ietfa.amsl.com>; Thu, 6 Feb 2014 09:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.036
X-Spam-Level:
X-Spam-Status: No, score=-15.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ChIFElseklKV for <idr@ietfa.amsl.com>; Thu, 6 Feb 2014 09:51:13 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 2C19A1A013C for <idr@ietf.org>; Thu, 6 Feb 2014 09:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3388; q=dns/txt; s=iport; t=1391709073; x=1392918673; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=MaZp4vqb1U14gfT0JwSzID4/fTilaAnacvfnlbJz+Cs=; b=AY50iqS++7vVUb1C7V6rK5fR4iRmaXxNL+8Z1e4gcYp4J6B1e5mh8oGm ZFw7BoUP9uS5P6FgKEgPlvFb89qr/f4Hpv5Q4wd/MLPjVQ12pW2UDXalW yhXMBH34OjKDF864nLElw1Y06j/mTZtrjaGgrEcbzfs0SVj7RjSPVU54i 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAGrK81KtJV2b/2dsb2JhbABZgw44Vb1MgQ0WAXSDfQEBAQQBAQE3NAsSAQgOCh43CyUCBAENBYgEDcZFEwSPEgeENgSUM4NjkhSDK4Iq
X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="299335301"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 06 Feb 2014 17:51:12 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s16HpBS8026707 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 6 Feb 2014 17:51:11 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.117]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Thu, 6 Feb 2014 11:51:11 -0600
From: "Keyur Patel (keyupate)" <keyupate@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Susan Hares <shares@ndzh.com>
Thread-Topic: [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-06.txt
Thread-Index: AQHPI2QEDal1f7T6ogADUl2weXy9pg==
Date: Thu, 06 Feb 2014 17:51:10 +0000
Message-ID: <CF190B56.62E01%keyupate@cisco.com>
In-Reply-To: <20140206161054.GE23551@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [128.107.163.63]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0C473FB20B8B4E43A453FACBD45E6966@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-06.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 06 Feb 2014 17:51:16 -0000
Hi Jeff, As part of rev 6, we added the following to Section 4: <snip> The following procedures are specified in order to simplify the interaction with the BGP Graceful Restart [RFC4724]. For a BGP speaker that supports the BGP Graceful Restart, it MUST NOT send a BoRR for an AFI/SAFI to a neighbor before it sends the EOR for the AFI/SAFI to the neighbor. A BGP speaker that has received the Graceful Restart Capability from its neighbor, MUST ignore any BoRRs for an AFI/SAFI from the neighbor before the speaker receives the EoR for the given AFI/SAFI from the neighbor. The BGP speaker SHOULD log an error of the condition for further analysis. <snip> Regards, Keyur On 2/6/14 8:10 AM, "Jeffrey Haas" <jhaas@pfrc.org> wrote: >On Thu, Feb 06, 2014 at 10:39:27AM -0500, Susan Hares wrote: >> Jeff: >> >> Please provide more details on your opinion on this information to the >>list: > >Sure. :-) > >> "Personally, I think it'd be wise to not process the enhanced RR >>procedures >> until GR is complete but I think that can be an implementation >>decision." >> (The justification is that there's a *lot* of work going on while >>processing >> GR and it's more valuable to get RIBs in some initial state of >> synchronization rather than worry about trying to fill in holes that >>might >> be present in the midst of it.) > >When a router that is assisting with a graceful restart, it has to do >several expensive things: >- Mark all routes received from that peer stale. >- Receive all routes again from that peer. >- Upon EoR (per family), sweep all stale routes not otherwise refreshed. > >In a non-multisession peering environment, you have one TCP socket between >you and the restarting peer. Presuming more than one AFI/SAFI negotiated >(lets say IPv4 unicast and L3VPN), even if you've finished refreshing IPv4 >unicast and could service a enhanced route refresh for that family, you're >still doing a lot of work trying to shove routes down the socket for >L3VPN. > >Even if you presume you ignore CPU or route-queueing efficiencies for an >implementation (let's say that some IPv4 Unicast is queued ahead of other >stuff), to service the refresh for those important routes you'd still push >off initial convergence of L3VPN. Whether this is wise is clearly an >implementation choice. > >Implementations are free to interleave queued routes as they wish and >there >are competing motivations as to why they'd want to servicing things in a >given way. But in abstract, delaying initial convergence seems unwise. > >An implementation would be free to queue the work requested for a enhanced >route refresh and not interrupt GR resync. That requires no changes to >the >spec. > >The spec could offer the opinion that you probably should do this, rather >than allowing a refresh to interrupt GR procedures (which impact timers) >by >reinserting routes that have been sent at least once into the queue. But >that gets pretty deep into implementation. Trying to be normative here >(RFC >2119 language) seems unwise since it simply puts an implementor into a >pedantic vice useful only to make test tool vendors happy. > >-- Jeff >_______________________________________________ >Idr mailing list >Idr@ietf.org >https://www.ietf.org/mailman/listinfo/idr
- [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-0… Keyur Patel (keyupate)
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Susan Hares
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Jeffrey Haas
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Susan Hares
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Jeffrey Haas
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Keyur Patel (keyupate)
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Jakob Heitz
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Jeffrey Haas
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Keyur Patel (keyupate)
- Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refre… Jeffrey Haas
- [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-0… Susan Hares