Re: Advancing the Protocol and Morin Drafts

"HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> Fri, 03 October 2008 15:04 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 C3F633A684A; Fri, 3 Oct 2008 08:04: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 30E6928C12D for <l3vpn@core3.amsl.com>; Fri, 3 Oct 2008 08:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 zl3UNOi58iXd for <l3vpn@core3.amsl.com>; Fri, 3 Oct 2008 08:04:23 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id C3E493A684A for <l3vpn@ietf.org>; Fri, 3 Oct 2008 08:04:21 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com [155.132.6.75]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m93F49PC017983; Fri, 3 Oct 2008 17:04:20 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Fri, 3 Oct 2008 17:04:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C92569.4F530686"
Subject: Re: Advancing the Protocol and Morin Drafts
Date: Fri, 03 Oct 2008 17:04:10 +0200
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D7030DC281@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: AckjzpmzrMkfiu+aTgG+8oLsbXlffwBkNEBLAAJwrCQ=
From: HENDERICKX Wim <wim.henderickx@alcatel-lucent.be>
To: QIU Ray <Ray.Qiu@alcatel-lucent.com>, tme@multicasttech.com, l3vpn@ietf.org
X-OriginalArrivalTime: 03 Oct 2008 15:04:19.0768 (UTC) FILETIME=[4FD14B80:01C92569]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
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

Support

Cheers,
Wim
_________________
sent from blackberry

----- Original Message -----
From: l3vpn-bounces@ietf.org <l3vpn-bounces@ietf.org>
To: tme@multicasttech.com <tme@multicasttech.com>; l3vpn@ietf.org <l3vpn@ietf.org>
Cc: rcallon@juniper.net <rcallon@juniper.net>
Sent: Fri Oct 03 15:53:29 2008
Subject: Re: Advancing the Protocol and Morin Drafts

Support

Cheers,
Ray

----- Original Message -----
From: l3vpn-bounces@ietf.org <l3vpn-bounces@ietf.org>
To: l3vpn@ietf.org <l3vpn@ietf.org>
Cc: Ross Callon <rcallon@juniper.net>
Sent: Wed Oct 01 09:04:07 2008
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