RE: Advancing the Protocol and Morin Drafts

"NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com> Fri, 10 October 2008 23:21 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 AB3953A6965; Fri, 10 Oct 2008 16:21:25 -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 B00473A6A97 for <l3vpn@core3.amsl.com>; Fri, 10 Oct 2008 16:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 xzs28EWevpUa for <l3vpn@core3.amsl.com>; Fri, 10 Oct 2008 16:21:24 -0700 (PDT)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.245.3]) by core3.amsl.com (Postfix) with ESMTP id C226C3A6965 for <l3vpn@ietf.org>; Fri, 10 Oct 2008 16:21:23 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: mnapierala@att.com
X-Msg-Ref: server-5.tower-146.messagelabs.com!1223680929!7212642!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 19921 invoked from network); 10 Oct 2008 23:22:10 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-5.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 10 Oct 2008 23:22:10 -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 m9ANM9YJ027259; Fri, 10 Oct 2008 19:22:09 -0400
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com [144.155.43.107]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m9ANM3LE027230; Fri, 10 Oct 2008 19:22:04 -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: Fri, 10 Oct 2008 19:22:04 -0400
Message-ID: <2F1DE4DFCFF32144B771BD2C246E6A20A5F328@misout7msgusr7e.ugd.att.com>
In-Reply-To: <3525C9833C09ED418C6FD6CD9514668C04DBF1EE@emailwf1.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: Ackq22IVXcYVaWuNTVSpYzh1QFICugAAoMdgAAWwnSoAAFaFwAADKpfAAAqcyhA=
References: <C5154047.CB15%benjamin.niven-jenkins@bt.com><DD7E9F364F33B54881C225192D4872D7A878DE@xmb-rtp-211.amer.cisco.com> <3525C9833C09ED418C6FD6CD9514668C04DBF1EE@emailwf1.jnpr.net>
From: "NAPIERALA, MARIA H, ATTLABS" <mnapierala@att.com>
To: Ross Callon <rcallon@juniper.net>
Cc: 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

Ross,
regarding
>[..] 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. They have to be an integral part of the solution.
Otherwise we will have to revisit the MVPN for the third time and such
opportunity will not come any time soon, if ever. This will ultimately
decide about the success (or lack of it) of this technology. 
And an IETF recommendations or requirements draft should not ignore such
capabilities.

Maria