Re: Advancing the Protocol and Morin Drafts

Thomas Morin <thomas.morin@orange-ftgroup.com> Wed, 22 October 2008 14:51 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 A5D4F28C104; Wed, 22 Oct 2008 07:51: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 E083F28C104 for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 07:51:00 -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 v0bM1bf7430R for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 07:50:59 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by core3.amsl.com (Postfix) with ESMTP id 61CF03A698A for <l3vpn@ietf.org>; Wed, 22 Oct 2008 07:50:59 -0700 (PDT)
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Oct 2008 16:51:51 +0200
Received: from [10.193.15.26] ([10.193.15.26]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Oct 2008 16:51:52 +0200
Subject: Re: Advancing the Protocol and Morin Drafts
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <2B7BA8FF-2819-451D-B018-5EB9DFFE764B@cisco.com>
References: <0E3033029745FB4C8BE6F1A3752FAE59E791DF@misout7msgusr7b.ugd.att.com> <1224680522.20832.74.camel@l-at11168.FTRD> <2B7BA8FF-2819-451D-B018-5EB9DFFE764B@cisco.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange Labs
Date: Wed, 22 Oct 2008 16:51:51 +0200
Message-Id: <1224687111.20832.82.camel@l-at11168.FTRD>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Oct 2008 14:51:52.0154 (UTC) FILETIME=[B80DB3A0:01C93455]
Cc: Ross Callon <rcallon@juniper.net>, L3VPN <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

Hi Ice,

IJsbrand Wijnands :
> 
> Thomas Morin:
> >
> > Most importantly, I would like to highlight the fact that, AFAICT the
> > people opposing the path proposed by the chairs have not proposed an
> > alternative that would help the working group push to the IESG, a  
> > set of documents describing a multicast VPN solution that vendors can  
> > implement and that would inter-operate.
> 
> That is not true, Cisco posted the draft-rosen-l3vpn-mvpn- 
> profiles-01, which documents very precisely how the PIM based  
> solutions work. And we are more then willing to add a BGP profile to  
> it with help of the people that prefer a BGP approach.

No, that would not describe "a multicast VPN solution", but multiple
ones.

> [...]  
> Each customer can choose the preferred approach and talk to the  
> vendor for an implementation.

For many operators its not "the vendor" but multiple vendors, and that's
why many operators (and apparently other IETF contributors too) see an
interest in standardizing one solution, with options where needed, and
not multiple profiles.

-Thomas