RE Advancing the Protocol and Morin Drafts

"Bitar, Nabil N." <nabil.n.bitar@verizon.com> Thu, 23 October 2008 03:53 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 8804C3A692F; Wed, 22 Oct 2008 20:53:16 -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 20A1A3A692F for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 20:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.299, 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 fhnx9EvltD8r for <l3vpn@core3.amsl.com>; Wed, 22 Oct 2008 20:53:15 -0700 (PDT)
Received: from tpamail2.verizon.com (tpamail2.verizon.com [192.76.82.136]) by core3.amsl.com (Postfix) with ESMTP id 0D84C3A6922 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 20:53:14 -0700 (PDT)
Received: from smtpftw3.verizon.com (smtpftw3.verizon.com [138.83.140.92]) by tpamail2.verizon.com (8.13.3/8.13.3) with ESMTP id m9N3sWIC010081 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 23:54:32 -0400 (EDT)
Received: from tpaintrmemf3.verizon.com (tpaintrmemf3.verizon.com [138.83.67.58]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id m9N3sWk1013273 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 23:54:32 -0400 (EDT)
Received: from tpaintrmemf3.verizon.com (unknown [127.0.0.1]) by tpaintrmemf3.verizon.com (Symantec Mail Security) with ESMTP id ADF6F528002 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 23:54:31 -0400 (EDT)
X-AuditID: 8a53433a-acbdfbb000000647-47-48fff577a56f
Received: from smtpftw3.verizon.com (unknown [138.83.140.92]) by tpaintrmemf3.verizon.com (EMF) with ESMTP id 7A7904E4002 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 23:54:31 -0400 (EDT)
Received: from FHDP1CCMXCG02.us.one.verizon.com ([166.68.240.34]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id m9N3sVXO013268 for <l3vpn@ietf.org>; Wed, 22 Oct 2008 23:54:31 -0400 (EDT)
Received: from FHDP1CCMXCV02.us.one.verizon.com ([166.68.240.12]) by FHDP1CCMXCG02.us.one.verizon.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Oct 2008 23:54:31 -0400
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_01C934C3.0D4FD10B"
Subject: RE Advancing the Protocol and Morin Drafts
Date: Wed, 22 Oct 2008 23:54:30 -0400
Message-ID: <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/g==
From: "Bitar, Nabil N." <nabil.n.bitar@verizon.com>
To: l3vpn@ietf.org
X-OriginalArrivalTime: 23 Oct 2008 03:54:31.0158 (UTC) FILETIME=[0DCD1160:01C934C3]
X-Brightmail-Tracker: AAAAAA==
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. 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