Re: Advancing the Protocol and Morin Drafts

Dino Farinacci <dino@cisco.com> Sun, 12 October 2008 01:11 UTC

Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3CF83A67D2; Sat, 11 Oct 2008 18:11:39 -0700 (PDT)
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7B9A3A679C for <l3vpn@core3.amsl.com>; Sat, 11 Oct 2008 18:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.065
X-Spam-Level:
X-Spam-Status: No, score=-6.065 tagged_above=-999 required=5 tests=[AWL=0.534, 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 RonNfPYlzzqd for <l3vpn@core3.amsl.com>; Sat, 11 Oct 2008 18:11:37 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id BB9173A67E5 for <l3vpn@ietf.org>; Sat, 11 Oct 2008 18:11:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,395,1220227200"; d="scan'208";a="173393286"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 12 Oct 2008 01:12:27 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9C1CRMK025872; Sat, 11 Oct 2008 18:12:27 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m9C1CRAd010872; Sun, 12 Oct 2008 01:12:27 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Oct 2008 18:12:27 -0700
Received: from [10.0.0.25] ([10.21.115.207]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Oct 2008 18:12:27 -0700
Message-Id: <9081B578-BA39-4DB9-AAC7-B0A5D02C113D@cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: "Drake, John E" <John.E.Drake2@boeing.com>
In-Reply-To: <51661468CBD1354294533DA79E85955A605B97@XCH-SW-5V2.sw.nos.boeing.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: Advancing the Protocol and Morin Drafts
Date: Sat, 11 Oct 2008 18:12:26 -0700
References: <51661468CBD1354294533DA79E85955A605B97@XCH-SW-5V2.sw.nos.boeing.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 12 Oct 2008 01:12:27.0112 (UTC) FILETIME=[97462680:01C92C07]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1966; t=1223773948; x=1224637948; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20Advancing=20the=20Protocol=20and=20Mori n=20Drafts |Sender:=20; bh=Nd6dAPiejuHDJN00/gSUegbKOh4PuJBioGqOxKcLO5o=; b=FzxfM4Bzhtu/QwAIYCg4U082PGSlvIlgCJjZU/Ctzpu754ep9E5GnCQBbW PHdMT76jKQMfePCAVMVksrhYteojih3/Y5ODOummJQZF8v/inimv8JBglr5P aEZRAp2yk1MhZesbxo/tzO7QHJQpcNGOfKxoTvWn2MpvvhSeHTszo=;
Authentication-Results: sj-dkim-1; header.From=dino@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: rcallon@juniper.net, yakov@juniper.net, l3vpn@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

It should have been clear. And if it is was not, then you can't even  
come close to claiming success.

Dino

On Oct 11, 2008, at 12:55 PM, Drake, John E wrote:

> And your point is?
>
> John Drake
> Boeing Satellite Systems
> 2260 East Imperial Highway MC W-S05-P208
> El Segundo, CA 90245
> john.e.drake2@boeing.com
> (412) 370-3108
>
> ----- Original Message -----
> From: Dino Farinacci <dino@cisco.com>
> To: Yakov Rekhter <yakov@juniper.net>
> Cc: Ross Callon <rcallon@juniper.net>; l3vpn@ietf.org <l3vpn@ietf.org>
> Sent: Fri Oct 10 16:35:11 2008
> Subject: Re: Advancing the Protocol and Morin Drafts
>
> Define success Yakov?
>
> It is not at all clear, and has never been proved to me this service
> is *profitable*. It may be generating revenue but the cost of running
> the service must be considered as well.
>
> Dino
>
> On Oct 10, 2008, at 9:08 AM, Yakov Rekhter wrote:
>
>> Prasanna,
>>
>>> I vote NO.
>>>
>>> Being in AT&T Advanced Tier support group and having supported the
>>> MVPN
>>> core for the last 2 years, I can clearly say that we need a solution
>>> such as PIM-BiDir that can reduce the number of multicast states in
>>> the
>>> PEs to be able to scale the Groups X Sources x OILs explosion for  
>>> our
>>> very large Enterprise customers.   We definitely do not want to
>>> tweak a
>>> crucial protocol like BGP of which our scale is 2 Million VPNV4
>>> routes
>>> in the US alone.
>>
>> On the subject of "we definitely do not want to tweak", I'd like
>> to remind you that during the early days of 2547 VPNs some of its
>> opponents were saying that they are against 2547 VPNs because they
>> do not want to "tweak" such a crucial protocol as BGP to carry VPNv4
>> routes.
>>
>> Today AT&T has "2 million VPNv4 routes in the US alone" all carried
>> in BGP, and a successful 2547 VPN service. None of this would be
>> possible if we would not tweak BGP.
>>
>> Yakov.
>