RE: Advancing the Protocol and Morin Drafts

"RAMSAROOP, JEEWAN P, ATTLABS" <jramsaroop@att.com> Mon, 13 October 2008 21:55 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 9B60C3A69DB; Mon, 13 Oct 2008 14:55:01 -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 0EC423A69DB for <l3vpn@core3.amsl.com>; Mon, 13 Oct 2008 14:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level:
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 t+Yw04jzZpZO for <l3vpn@core3.amsl.com>; Mon, 13 Oct 2008 14:55:00 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id 497BB3A67A1 for <l3vpn@ietf.org>; Mon, 13 Oct 2008 14:55:00 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jramsaroop@att.com
X-Msg-Ref: server-12.tower-120.messagelabs.com!1223934899!42192368!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 29745 invoked from network); 13 Oct 2008 21:55:00 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-12.tower-120.messagelabs.com with AES256-SHA encrypted SMTP; 13 Oct 2008 21:55:00 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m9DLsw84020055; Mon, 13 Oct 2008 17:54:59 -0400
Received: from misout7msgusr7b.ugd.att.com (misout7msgusr7b.ugd.att.com [144.155.43.104]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m9DLsrjZ020009; Mon, 13 Oct 2008 17:54:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Advancing the Protocol and Morin Drafts
Date: Mon, 13 Oct 2008 17:54:51 -0400
Message-ID: <EFF1871D0BC028439D31795599E82B93F6B339@misout7msgusr7b.ugd.att.com>
In-Reply-To: <200810101608.m9AG86M66693@magenta.juniper.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: Ackq8qjvlOeEr6trTxKGfLS8ne23TQCiwkMg
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com><2F1DE4DFCFF32144B771BD2C246E6A20E721CD@misout7msgusr7e.ugd.att.com> <200810101608.m9AG86M66693@magenta.juniper.net>
From: "RAMSAROOP, JEEWAN P, ATTLABS" <jramsaroop@att.com>
To: Yakov Rekhter <yakov@juniper.net>, "RAMACHANDRAN, PRASANNA, ATTOPS" <prasanna@att.com>
Cc: Ross Callon <rcallon@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

Yakov:

How does accepting of Morin's draft improve the profitability of the
current VPN/mVPN service?

Jeewan 

-----Original Message-----
From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
Of Yakov Rekhter
Sent: Friday, October 10, 2008 12:08 PM
To: RAMACHANDRAN, PRASANNA, ATTOPS
Cc: Ross Callon; l3vpn@ietf.org
Subject: Re: Advancing the Protocol and Morin Drafts 

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.