RE: Advancing the Protocol and Morin Drafts

"Ahmed Omran" <aemran@juniper.net> Sat, 18 October 2008 22:09 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 37FC53A67E2; Sat, 18 Oct 2008 15:09:41 -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 5E8A03A67E2 for <l3vpn@core3.amsl.com>; Sat, 18 Oct 2008 15:09:40 -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 ZfpLWbIfpCQh for <l3vpn@core3.amsl.com>; Sat, 18 Oct 2008 15:09:39 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7ob116.obsmtp.com [64.18.2.218]) by core3.amsl.com (Postfix) with ESMTP id 6B3043A67B4 for <l3vpn@ietf.org>; Sat, 18 Oct 2008 15:09:38 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP; Sat, 18 Oct 2008 15:10:19 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 18 Oct 2008 15:10:36 -0700
Received: from emailfeemea2.jnpr.net ([172.26.192.142]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 18 Oct 2008 15:10:36 -0700
Received: from emailemea4.jnpr.net ([172.26.192.133]) by emailfeemea2.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Sat, 18 Oct 2008 23:10:33 +0100
Content-class: urn:content-classes:message
Subject: RE: Advancing the Protocol and Morin Drafts
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 18 Oct 2008 23:10:31 +0100
Message-ID: <ACC9FC68D7C80140AE63F891430B55BD07D8D636@emailemea4.jnpr.net>
In-Reply-To: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: Ackjzp3ac+fFiz/9Rxm/rrjweuzwwwLzyg4A
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
From: Ahmed Omran <aemran@juniper.net>
To: Marshall Eubanks <tme@multicasttech.com>, l3vpn@ietf.org
X-OriginalArrivalTime: 18 Oct 2008 22:10:33.0155 (UTC) FILETIME=[56F0B930:01C9316E]
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

SUPPORT

Cheers,

/Ahmed 



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