RE: Advancing the Protocol and Morin Drafts

Thomas Morin <thomas.morin@orange-ftgroup.com> Mon, 13 October 2008 08:25 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 6C96A3A682A; Mon, 13 Oct 2008 01:25:27 -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 E8F0A3A659B for <l3vpn@core3.amsl.com>; Mon, 13 Oct 2008 01:25:25 -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 6d9lse1VPVtQ for <l3vpn@core3.amsl.com>; Mon, 13 Oct 2008 01:25:25 -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 920FB3A657C for <l3vpn@ietf.org>; Mon, 13 Oct 2008 01:25:24 -0700 (PDT)
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Oct 2008 10:25:21 +0200
Received: from [10.193.15.31] ([10.193.15.31]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Oct 2008 10:25:20 +0200
Subject: RE: Advancing the Protocol and Morin Drafts
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
In-Reply-To: <2F1DE4DFCFF32144B771BD2C246E6A20A5F328@misout7msgusr7e.ugd.att.com>
References: <C5154047.CB15%benjamin.niven-jenkins@bt.com> <DD7E9F364F33B54881 C225192D4872D7A878DE@xmb-rtp-211.amer.cisco.com> <3525C9833C09ED418C6FD6CD9514668C04DBF1EE@emailwf1.jnpr.net> <2F1DE4DFCFF32144B771BD2C246E6A20A5F328@misout7msgusr7e.ugd.att.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange Labs
Date: Mon, 13 Oct 2008 10:25:20 +0200
Message-Id: <1223886320.5574.46.camel@l-at11168.FTRD>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Oct 2008 08:25:20.0662 (UTC) FILETIME=[3B211B60:01C92D0D]
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

Hi Maria,

NAPIERALA, MARIA H, ATTLABS :
> >[..] whether to accept a new set of
> >requirements which are likely to lead to a different solution (which
> >might in the future lead to an additional profile)
> 
> if the MVPN solution does not lay out the correct foundation to support
> basic multicast capabilities in VPN context like PIM-Bidir, Anycast-RP,
> or anycast sourcing then those capabilities cannot be just added on
> after the fact. 

*If* you believe that the solutions specified do not include what you
need or have limitations limiting their applicability, then you should
make statements about what need to be changed in these drafts, now, or
during their last call.

This is _unrelated_ to choosing, inside the solution draft, a set of
options mandatory to implement.

(Now, the solution drafts -- independently of the approach used for the
different building blocks --  do completely support PIM-Bidir,
Anycast-RP, and anycast sourcing)

-Thomas