Re: Advancing the Protocol and Morin Drafts

Ron Bonica <rbonica@juniper.net> Mon, 13 October 2008 17:38 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 08C473A6AC4; Mon, 13 Oct 2008 10:38:54 -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 6A4BD3A6820 for <l3vpn@core3.amsl.com>; Mon, 13 Oct 2008 10:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 dlCFI4tSlQk3 for <l3vpn@core3.amsl.com>; Mon, 13 Oct 2008 10:38:52 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id 441853A6AC4 for <l3vpn@ietf.org>; Mon, 13 Oct 2008 10:38:52 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP; Mon, 13 Oct 2008 10:38:56 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp02.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 13 Oct 2008 10:34:50 -0700
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 13 Oct 2008 10:34:50 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 13 Oct 2008 13:34:49 -0400
Received: from [172.23.1.193] ([172.23.1.193] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Oct 2008 13:34:44 -0400
Message-ID: <48F386AE.1090201@juniper.net>
Date: Mon, 13 Oct 2008 13:34:38 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dino Farinacci <dino@cisco.com>
Subject: Re: Advancing the Protocol and Morin Drafts
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com> <2F1DE4DFCFF32144B771BD2C246E6A20E721CD@misout7msgusr7e.ugd.att.com> <200810101608.m9AG86M66693@magenta.juniper.net> <EE8ECF15-01CD-4E7A-AE6F-D878688FCDE7@cisco.com>
In-Reply-To: <EE8ECF15-01CD-4E7A-AE6F-D878688FCDE7@cisco.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Oct 2008 17:34:44.0189 (UTC) FILETIME=[FAEC28D0:01C92D59]
Cc: Ross Callon <rcallon@juniper.net>, Yakov Rekhter <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

Dino,

When you say "this service", do you refer to the L3VPN unicast service,
the L3VPN multicast service, or an L3VPN service that includes both
unicast and multicast? Or all of the above?

                              Ron


Dino Farinacci wrote:
> 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.
> 
>