RE: RE Advancing the Protocol and Morin Drafts

"LEVRAU, LIEVEN \(LIEVEN\)" <llevrau@alcatel-lucent.com> Thu, 23 October 2008 13:57 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 A4C193A6A0A; Thu, 23 Oct 2008 06:57:21 -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 3BAA73A698C for <l3vpn@core3.amsl.com>; Thu, 23 Oct 2008 06:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[AWL=1.197, BAYES_00=-2.599, 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 Rj1pb+swdVcS for <l3vpn@core3.amsl.com>; Thu, 23 Oct 2008 06:57:13 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 46E043A68C1 for <l3vpn@ietf.org>; Thu, 23 Oct 2008 06:57:13 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m9NDwO6s010829; Thu, 23 Oct 2008 08:58:29 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Oct 2008 08:58:06 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.29]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Oct 2008 15:58:03 +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_01C93517.5D992904"
Subject: RE: RE Advancing the Protocol and Morin Drafts
Date: Thu, 23 Oct 2008 15:58:01 +0200
Message-ID: <972138A9A2BE554A8710BB4F3E4B03A5D9CF00@DEEXC1U02.de.lucent.com>
In-Reply-To: <4B19CE71813C034F8961D9E51324522E01203469@FHDP1CCMXCV02.us.one.verizon.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RE Advancing the Protocol and Morin Drafts
Thread-Index: Ack0ww2tVG1fEzFMSvqkRdA5sJAW/gAVEUOg
References: <4B19CE71813C034F8961D9E51324522E01203469@FHDP1CCMXCV02.us.one.verizon.com>
From: "LEVRAU, LIEVEN (LIEVEN)" <llevrau@alcatel-lucent.com>
To: "Bitar, Nabil N." <nabil.n.bitar@verizon.com>, l3vpn@ietf.org
X-OriginalArrivalTime: 23 Oct 2008 13:58:03.0236 (UTC) FILETIME=[5DE1AA40:01C93517]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
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

./

Lieven

 

From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf
Of Bitar, Nabil N.
Sent: 23 October 2008 05:55
To: l3vpn@ietf.org
Subject: RE Advancing the Protocol and Morin Drafts

 

Support. Progressing the draft should also consider the inclusion of
additional requirements that have risen as needed to be supported by an
MVPN solution

Thanks,

Nabil

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