Re: [Idr] draft-jakma-mrai-dep-00 (fwd)

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Wed, 26 November 2008 17:17 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5A143A695F; Wed, 26 Nov 2008 09:17:36 -0800 (PST)
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 4E6033A695F for <idr@core3.amsl.com>; Wed, 26 Nov 2008 09:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.322
X-Spam-Level:
X-Spam-Status: No, score=-6.322 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 OeLPMRkszgQ6 for <idr@core3.amsl.com>; Wed, 26 Nov 2008 09:17:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 3D35F3A6836 for <idr@ietf.org>; Wed, 26 Nov 2008 09:17:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,670,1220227200"; d="scan'208";a="29164056"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 26 Nov 2008 17:17:31 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mAQHHVG7001208; Wed, 26 Nov 2008 12:17:31 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mAQHHVnc016231; Wed, 26 Nov 2008 17:17:31 GMT
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Nov 2008 12:17:30 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 26 Nov 2008 12:17:26 -0500
Message-ID: <15B86BC7352F864BB53A47B540C089B6069A7946@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <2815BD5B-2006-4074-9613-8F5D580E983E@juniper.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Idr] draft-jakma-mrai-dep-00 (fwd)
Thread-Index: AclPjUww7Wpu4fc1QruLnBgrDAgnXgAXE88Q
References: <200811252329.mAPNTTM46473@magenta.juniper.net><20081126001652.GB12535@slice><200811260140.mAQ1eXM09692@magenta.juniper.net><20081126042010.GA14608@slice> <2815BD5B-2006-4074-9613-8F5D580E983E@juniper.net>
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: Pedro Marques <roque@juniper.net>, Jeffrey Haas <jhaas@pfrc.org>
X-OriginalArrivalTime: 26 Nov 2008 17:17:30.0929 (UTC) FILETIME=[DD3A3210:01C94FEA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2542; t=1227719851; x=1228583851; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rajiva@cisco.com; z=From:=20=22Rajiv=20Asati=20(rajiva)=22=20<rajiva@cisco.com > |Subject:=20RE=3A=20[Idr]=20draft-jakma-mrai-dep-00=20(fwd) |Sender:=20 |To:=20=22Pedro=20Marques=22=20<roque@juniper.net>,=20=22Je ffrey=20Haas=22=20<jhaas@pfrc.org>; bh=I7bmGLJvpkgk57txoUevZIN9H6xhPoC5LPSbQJughas=; b=MMywdmKW1qQkxQwIlJYQYjeg5Sa89/5vMGZrzMki2cBdKVY9elNImlsDrp HFjmrCtcjqqK+Tq7y/NMICLfbW3OMkAHNtSpaYt/S3qXfDxHoJ6xHSouFaRU E+lwGgwCCG;
Authentication-Results: rtp-dkim-1; header.From=rajiva@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: Yakov Rekhter <yakov@juniper.net>, idr@ietf.org
Subject: Re: [Idr] draft-jakma-mrai-dep-00 (fwd)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi Pedro,

Your assessment is correct. 

However, within a particular network (say, providing BGP/VPN service),
the reachability and unreachability may not translate to a single event.
In the below simplified topology, CE1 is dual-homed to PE1 and PE2
(having the VRFs with unique RDs) -

 
      CE1-----PE1------------PE3-----CE
	 \------PE2------------/

CE1-PE1 link failure results in withdrawn of bunch of routes from PE1 to
PE3, which needs to receive this event as quickly as possible (related
to any other previous advertisements PE1 may have sent to PE3). 

This stays as a single event, even if there are RR in the network (given
the unique RD per VRF per PE).

Needless to say that the above scenario becomes trivial with MRAI = 0
for iBGP.

Cheers,
Rajiv


> -----Original Message-----
> From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of
> Pedro Marques
> Sent: Wednesday, November 26, 2008 1:08 AM
> To: Jeffrey Haas
> Cc: Yakov Rekhter; idr@ietf.org
> Subject: Re: [Idr] draft-jakma-mrai-dep-00 (fwd)
> 
> 
> On Nov 25, 2008, at 8:20 PM, Jeffrey Haas wrote:
> 
> > Yakov,
> >
> > On Tue, Nov 25, 2008 at 05:40:33PM -0800, Yakov Rekhter wrote:
> >> With my WG chair hat off, I think the document more or less
> satisfies
> >> the requirements. The only two change I would suggest to make are
> >> (a) to
> >> eliminate a special case for Withdrawn Routes (this is based on
> >> some discussion that happened few years ago initiated by Pedro
> >> Marques),
> >
> > By this, do you mean you don't believe that MRAI should be
separately
> > configurable for reachability and unreachability?
> 
> The rational for not treating them differently is that a single event
> as it propagates through the network gets expressed as both
> reachability and withdrawal information.
> 
> The typical example being an SP that acquires a newly preferred peer
> route which them causes it to send withdrawals to other peers
> (reachable converts to unreachable).
> 
> My understanding is that this behavior has been well document in
> practical observations of BGP convergence.
> 
> In general my recommendation for MRAI values would be 0 for eBGP and 0
> for iBGP. As the draft correctly explains calculating a value that
> best fits the network is a very tricky business.
> 
> regards,
>    Pedro.
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr