RE: Advancing the Protocol and Morin Drafts

"ROSENBERG, ERIC, ATTLABS" <ericr@att.com> Thu, 09 October 2008 01:45 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 49B973A6C1E; Wed, 8 Oct 2008 18:45:18 -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 C15EA3A68B3 for <l3vpn@core3.amsl.com>; Wed, 8 Oct 2008 10:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level:
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 bygxb52MneE6 for <l3vpn@core3.amsl.com>; Wed, 8 Oct 2008 10:44:39 -0700 (PDT)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.245.3]) by core3.amsl.com (Postfix) with ESMTP id CA7063A6847 for <l3vpn@ietf.org>; Wed, 8 Oct 2008 10:44:38 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ericr@att.com
X-Msg-Ref: server-7.tower-146.messagelabs.com!1223487901!1091586!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 3549 invoked from network); 8 Oct 2008 17:45:01 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-7.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 8 Oct 2008 17:45:01 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m98HixBr018316; Wed, 8 Oct 2008 13:45:01 -0400
Received: from misout7msgusr7e.ugd.att.com (misout7msgusr7e.ugd.att.com [144.155.43.107]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m98HitdH018173; Wed, 8 Oct 2008 13:44:55 -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, 08 Oct 2008 13:44:30 -0400
Message-ID: <5F4FC71B2BB5CC4F8FAD055334F369A6AB87A1@misout7msgusr7e.ugd.att.com>
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: Ackjzp54ug9IjSBWQh+f5oNpsfcOngFnqC9g
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
From: "ROSENBERG, ERIC, ATTLABS" <ericr@att.com>
To: Marshall Eubanks <tme@multicasttech.com>, l3vpn@ietf.org
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

 opposed - I do not support  this approach

Eric Rosenberg

-----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