RE: Advancing the Protocol and Morin Drafts

"HEMIGE Venu" <Venu.Hemige@alcatel-lucent.com> Fri, 03 October 2008 10:30 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 5533F3A6AD8; Fri, 3 Oct 2008 03:30:44 -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 A50833A6A97 for <l3vpn@core3.amsl.com>; Fri, 3 Oct 2008 03:00:33 -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 kcliB3uLMIRC for <l3vpn@core3.amsl.com>; Fri, 3 Oct 2008 03:00:32 -0700 (PDT)
Received: from audl953.usa.alcatel.com (audl953.usa.alcatel.com [143.209.238.162]) by core3.amsl.com (Postfix) with ESMTP id A32423A69DA for <l3vpn@ietf.org>; Fri, 3 Oct 2008 03:00:32 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl953.usa.alcatel.com (ALCANET) with ESMTP id m93A0eIu029778; Fri, 3 Oct 2008 05:00:40 -0500
Received: from USDALSMBS03.ad3.ad.alcatel.com ([172.22.216.11]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 05:00:40 -0500
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, 03 Oct 2008 05:00:27 -0500
Message-ID: <98E5EEEC1F4EF740912E44EA3022569A0E4DEFC8@USDALSMBS03.ad3.ad.alcatel.com>
In-Reply-To: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: Ackjzpe96CXE7svLTmurmO3/e5zrMwBcDspA
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
From: HEMIGE Venu <Venu.Hemige@alcatel-lucent.com>
To: Marshall Eubanks <tme@multicasttech.com>, l3vpn@ietf.org
X-OriginalArrivalTime: 03 Oct 2008 10:00:40.0134 (UTC) FILETIME=[E411C660:01C9253E]
X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34
X-Mailman-Approved-At: Fri, 03 Oct 2008 03:30:43 -0700
Cc: Ross Callon <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

Support. 

-----Original Message-----
From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
Of Marshall Eubanks
Sent: Wednesday, October 01, 2008 7:04 AM
To: l3vpn@ietf.org
Cc: Ross Callon
Subject: Advancing the Protocol and Morin Drafts 

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