RE: Advancing the Protocol and Morin Drafts

Thomas Morin <thomas.morin@orange-ftgroup.com> Tue, 14 October 2008 09:12 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 5416D3A6ACB; Tue, 14 Oct 2008 02:12:35 -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 6736D3A6ACB for <l3vpn@core3.amsl.com>; Tue, 14 Oct 2008 02:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 IUaXgVGJO224 for <l3vpn@core3.amsl.com>; Tue, 14 Oct 2008 02:12:33 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 3DEF43A67F8 for <l3vpn@ietf.org>; Tue, 14 Oct 2008 02:12:33 -0700 (PDT)
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Oct 2008 11:13:14 +0200
Received: from [10.193.15.193] ([10.193.15.193]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Oct 2008 11:13:15 +0200
Subject: RE: Advancing the Protocol and Morin Drafts
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: "RAMSAROOP, JEEWAN P, ATTLABS" <jramsaroop@att.com>
In-Reply-To: <EFF1871D0BC028439D31795599E82B93F6B339@misout7msgusr7b.ugd.att.com>
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com> <2F1DE4D FCFF32144B771BD2C246E6A20E721CD@misout7msgusr7e.ugd.att.com> <200810101608.m9AG86M66693@magenta.juniper.net> <EFF1871D0BC028439D31795599E82B93F6B339@misout7msgusr7b.ugd.att.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange Labs
Date: Tue, 14 Oct 2008 11:13:15 +0200
Message-Id: <1223975595.5406.63.camel@l-at11168.FTRD>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Oct 2008 09:13:15.0453 (UTC) FILETIME=[170D26D0:01C92DDD]
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

RAMSAROOP, JEEWAN P, ATTLABS :
>
> How does accepting of Morin's draft improve the profitability of the
> current VPN/mVPN service?

It is not exactly the question asked today, but if you understand why
standards are useful and that all solutions to a problem do not
necessarily have the same efficiency, then I think you'll find an answer
by yourself.

-Thomas



> -----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.