RE: Advancing the Protocol and Morin Drafts

"PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be> Fri, 10 October 2008 21:40 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 554C93A67F9; Fri, 10 Oct 2008 14:40:20 -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 D83A13A6822 for <l3vpn@core3.amsl.com>; Fri, 10 Oct 2008 14:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 45SJP8RRHGUl for <l3vpn@core3.amsl.com>; Fri, 10 Oct 2008 14:40:18 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id E84743A67A7 for <l3vpn@ietf.org>; Fri, 10 Oct 2008 14:40:17 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com [155.132.6.74]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9ALf24a013921; Fri, 10 Oct 2008 23:41:02 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 10 Oct 2008 23:41:02 +0200
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 23:37:06 +0200
Message-ID: <00275A5B436CA441900CB10936742A38012E066D@FRVELSMBS22.ad2.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: AckjzpvvwBKzpqcGS2OnYVeS5QvSTgHUVyVA
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
From: PAPADIMITRIOU Dimitri <Dimitri.Papadimitriou@alcatel-lucent.be>
To: Marshall Eubanks <tme@multicasttech.com>, l3vpn@ietf.org
X-OriginalArrivalTime: 10 Oct 2008 21:41:02.0752 (UTC) FILETIME=[E464AA00:01C92B20]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
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

not in favor.
-d. 

> -----Original Message-----
> From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] 
> On Behalf Of Marshall Eubanks
> Sent: Wednesday, October 01, 2008 4:04 PM
> 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
> 
>