Re: Advancing the Protocol and Morin Drafts

IJsbrand Wijnands <ice@cisco.com> Wed, 22 October 2008 14:39 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 139DF3A68D8; Wed, 22 Oct 2008 07:39:40 -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 DEEF23A68D8 for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 07:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 8eidd0Iiedpq for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 07:39:38 -0700 (PDT)
Received: from av-tac-bru.cisco.com (odd-brew.cisco.com [144.254.15.119]) by core3.amsl.com (Postfix) with ESMTP id B3F643A67F2 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 07:39:37 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id m9MEe3h21697; Wed, 22 Oct 2008 16:40:08 +0200 (CEST)
Received: from [10.55.191.152] (ams-iwijnand-8717.cisco.com [10.55.191.152]) by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id m9MEe3G21690; Wed, 22 Oct 2008 16:40:03 +0200 (CEST)
In-Reply-To: <1224680522.20832.74.camel@l-at11168.FTRD>
References: <0E3033029745FB4C8BE6F1A3752FAE59E791DF@misout7msgusr7b.ugd.att.com> <1224680522.20832.74.camel@l-at11168.FTRD>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <2B7BA8FF-2819-451D-B018-5EB9DFFE764B@cisco.com>
Content-Transfer-Encoding: 7bit
From: IJsbrand Wijnands <ice@cisco.com>
Subject: Re: Advancing the Protocol and Morin Drafts
Date: Wed, 22 Oct 2008 16:40:03 +0200
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
X-Mailer: Apple Mail (2.753.1)
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

Thomas,

>
> I'm slightly tired of hearing the same arguments in tens emails  
> from the
> same source, but I will still try to highlight a few misleading or  
> wrong
> statements (below).
>
> 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.

After last IETF I had hoped to see a proposal from the chairs to  
create 2 drafts, one documenting a PIM based solutions set, and an  
other based on BGP. Both moving forward on standards track. These  
documents don't need to make comparisons between BGP and PIM (as is  
done in the Morin draft), because this creates endless discussions  
and don't get us anywhere. It just needs to document how the  
different modules work together so that vendors can be interoperable.  
Each customer can choose the preferred approach and talk to the  
vendor for an implementation.

Thx,

Ice.