RE: Advancing the Protocol and Morin Drafts

<ketan.paralkar@bell.ca> Thu, 09 October 2008 14:00 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 87A2F3A6AAF; Thu, 9 Oct 2008 07:00:48 -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 EAEE73A6A6B for <l3vpn@core3.amsl.com>; Thu, 9 Oct 2008 07:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 U+XM42Yhldqo for <l3vpn@core3.amsl.com>; Thu, 9 Oct 2008 07:00:42 -0700 (PDT)
Received: from mail93.messagelabs.com (mail93.messagelabs.com [194.106.220.67]) by core3.amsl.com (Postfix) with ESMTP id 2C0073A68F9 for <l3vpn@ietf.org>; Thu, 9 Oct 2008 07:00:42 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ketan.paralkar@bell.ca
X-Msg-Ref: server-6.tower-93.messagelabs.com!1223560821!22213250!20
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [206.47.0.173]
Received: (qmail 7939 invoked from network); 9 Oct 2008 14:00:35 -0000
Received: from srp004376srs (HELO TLS.Exchange.Bell.ca) (206.47.0.173) by server-6.tower-93.messagelabs.com with RC4-SHA encrypted SMTP; 9 Oct 2008 14:00:35 -0000
Received: from hub03-wyn.bell.corp.bce.ca (142.182.199.49) by dm1c8f.exchange1.bell.ca (198.235.102.112) with Microsoft SMTP Server id 8.1.278.0; Thu, 9 Oct 2008 10:00:15 -0400
Received: from MBX08.bell.corp.bce.ca ([142.182.199.89]) by hub03-wyn.bell.corp.bce.ca ([142.182.199.49]) with mapi; Thu, 9 Oct 2008 10:00:13 -0400
From: ketan.paralkar@bell.ca
To: l3vpn@ietf.org
Date: Thu, 09 Oct 2008 10:00:12 -0400
Subject: RE: Advancing the Protocol and Morin Drafts
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: AckpsMOssLMpvRxeSLiNDP2Lqaer5AAZij1g
Message-ID: <EFAB6F21C0EA5D4A8AD8E43E7587C129709421B7@MBX08.bell.corp.bce.ca>
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com> <B6C00083-B29F-4B8B-97D5-194B0670509E@juniper.net>
In-Reply-To: <B6C00083-B29F-4B8B-97D5-194B0670509E@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: rcallon@juniper.net
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

I support.

Thanks

Ketan.






Ketan Paralkar MIET , CCIE 12179, JNCIS
Sr. Network Architect
BELL SYSTEMS & TECHNOLOGY
Technology Development
Bell Canada
76 Adelaide Street West, 15th Floor
Toronto, Ontario
M5H 1P6
Office  (416)-353-3227
e-mail : ketan.paralkar@bell.ca



> This email starts a 3 week call for input, to expire October 23, 2008,
> for the following steps:
>
> 1.) To accept draft-morin-l3vpn-mvpn-considerations-03 as a working
> group document;  and
>
> 2.) To turn this document into a requirements draft, with mandatory to
> implement features for an interoperable implementation. The authors
> have indicated that they are willing to do this.
>
> Our intention is, if this approach is accepted, to then begin WG last
> call to submit to the IESG for publication:
>
> draft-ietf-l3vpn-2547bis-mcast
> draft-ietf-l3vpn-2547bis-mcast-bgp
>
> We expect that these two documents will be submitted more or less as
> is
> (i.e., certainly with any new bug fixes or other necessary corrections
> and
> improvements, but without specific mandatory to implement feature
> description in those drafts).
>
> Please respond to the list with your recommendations for these two
> courses of action.
>
> Regards
> Marshall & Danny
>