RE: Advancing the Protocol and Morin Drafts

"Marco Rodrigues" <mprodrigues@juniper.net> Wed, 01 October 2008 18:32 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 96E683A6A92; Wed, 1 Oct 2008 11:32:34 -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 46E523A6405 for <l3vpn@core3.amsl.com>; Wed, 1 Oct 2008 11:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 p1KZ+B8WijVX for <l3vpn@core3.amsl.com>; Wed, 1 Oct 2008 11:16:48 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 6F75D3A6856 for <l3vpn@ietf.org>; Wed, 1 Oct 2008 11:16:47 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP; Wed, 01 Oct 2008 11:14:22 PDT
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Oct 2008 11:16:22 -0700
Received: from emailwf3.jnpr.net ([10.10.2.45]) by emailwf1.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 1 Oct 2008 14:16:21 -0400
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: Wed, 01 Oct 2008 14:16:21 -0400
Message-ID: <295627243C91274CBCE3C52BBB7E3D86D6134A@emailwf3.jnpr.net>
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: Ackjzpw2lOFd5/rLTxiyHpGyU5ri2AAIxuVw
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
From: Marco Rodrigues <mprodrigues@juniper.net>
To: Marshall Eubanks <tme@multicasttech.com>, l3vpn@ietf.org
X-OriginalArrivalTime: 01 Oct 2008 18:16:21.0380 (UTC) FILETIME=[CE684440:01C923F1]
X-Mailman-Approved-At: Wed, 01 Oct 2008 11:32:33 -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

I'm in support of this direction.

-mpr

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