Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt

Robert Raszuk <raszuk@CISCO.COM> Wed, 12 November 2003 14:16 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18417 for <ospf-archive@LISTS.IETF.ORG>; Wed, 12 Nov 2003 09:16:44 -0500 (EST)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <21.00C42A89@cherry.ease.lsoft.com>; Wed, 12 Nov 2003 9:16:53 -0500
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 60284626 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 12 Nov 2003 09:16:52 -0500
Received: from 171.71.176.71 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 12 Nov 2003 09:16:52 -0400
Received: from cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 12 Nov 2003 06:19:01 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hACEGnw5029653; Wed, 12 Nov 2003 06:16:50 -0800 (PST)
Received: from cisco.com (sjc-vpn1-255.cisco.com [10.21.96.255]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ANM46816; Wed, 12 Nov 2003 06:16:48 -0800 (PST)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <3F9E9379.3070602@redback.com> <3F9EAD95.9050101@cisco.com> <3F9EB8F2.10002@cisco.com> <20031110084404.A84355@sapphire.juniper.net> <3FAFFBEC.7090409@cisco.com> <20031111211412.Y12111@sapphire.juniper.net> <3FB1CBA8.2050608@cisco.com> <3FB1CE85.5040305@cisco.com> <3FB1DE2C.F38FCBE3@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3FB240D0.70506@cisco.com>
Date: Wed, 12 Nov 2003 15:16:48 +0100
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Robert Raszuk <raszuk@CISCO.COM>
Organization: Signature: http://www.employees.org/~raszuk/sig/
Subject: Re: draft-eng-nalawade-ospf-tunnel-cap-00.txt
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <3FB1DE2C.F38FCBE3@cisco.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Gargi,

 > core ipv4 routing. So let's not talk about BGP here.
 >
 > Reality is, in most generic implementations today, there is an order
 > of magnitude difference between OSPF and BGP.

Of course there is. And that's why we should not only talk about BGP
here comparing both solutions as about some massive and huge monster but
we do need to realize that Tunnel AFI/SAFI's properties and the number
of few NLRIs it needs to carry in comparison with thousands of ipv4 or
vpnv4 BGP carries is a very significant factor to keep in mind.

Cheers,
R.


 > Gargi Nalawade wrote:
 >
> Robert,
>
> Robert Raszuk wrote:
>
>>Sandy,
>>
>>
>>>In a VPN enviroment, OSPF converges in sub-seconds while BGP in minutes,
>>>OSPF can deliver the tunnel endpoint information much faster than BGP,
>>>enabling faster traffic reachibility.
>>
>>I can't agree with this statement.
>>
>>BGP convergence intra domain - note within _single_ domain can be in
>>fact almost as fast for tunnel AFI/SAFI then for OSPF. In fact with
>>default timers in OSPF and with prioritizing tunnel AFI/SAFI first (as
>>it should be the case) I could argue that even today with most BGP
>
>
> I dont quite agree with - 'prioritizing... as should be the case'. We
> have debated this in the past and you know my stance. The stance of
> multiple providers I have talked to, also seems to be the same. They
> want a simple, scalable BGP which does not affect/compromise on their
> core ipv4 routing. So let's not talk about BGP here.
>
> Reality is, in most generic implementations today, there is an order of
> magnitude difference between OSPF and BGP.
>
>
>>implementations it will converge faster then OSPF when the number of
>>your P routers is decent.
>
>
> Let's forget about the 'if's and 'when's for now. Plus convergence is
> not the only major driving factor. There is a need for a non-BGP solution
> expressed by the enterprise and provider space alike.
>
>
>>I think we could debate more - and yes this draft itself solves some
>>practical cases with not too big overhead for IGPs - but let's at least
>
>
> Ok. So you agree that this draft solves practical cases. Hear Ya!
>
> -Gargi
>