RE: Advancing the Protocol and Morin Drafts

"MEDAMANA, JOHN B, ATTOPS" <jmedamana@att.com> Fri, 24 October 2008 03:07 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 655E93A681D; Thu, 23 Oct 2008 20:07:26 -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 123753A681D for <l3vpn@core3.amsl.com>; Thu, 23 Oct 2008 20:07:25 -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, HTML_MESSAGE=0.001, 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 EZjQinrv4X-b for <l3vpn@core3.amsl.com>; Thu, 23 Oct 2008 20:07:24 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.245.115]) by core3.amsl.com (Postfix) with ESMTP id D48A13A6781 for <l3vpn@ietf.org>; Thu, 23 Oct 2008 20:07:23 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: jmedamana@att.com
X-Msg-Ref: server-3.tower-121.messagelabs.com!1224817722!32985367!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 6380 invoked from network); 24 Oct 2008 03:08:43 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-3.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 24 Oct 2008 03:08:43 -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 m9O38gV6004471 for <l3vpn@ietf.org>; Thu, 23 Oct 2008 23:08:42 -0400
Received: from misout7msgusr7d.ugd.att.com (misout7msgusr7d.ugd.att.com [144.155.43.106]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id m9O38gnY004468 for <l3vpn@ietf.org>; Thu, 23 Oct 2008 23:08:42 -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_01C93585.D1BA57AC"
Subject: RE: Advancing the Protocol and Morin Drafts
Date: Thu, 23 Oct 2008 23:08:40 -0400
Message-ID: <81E7EA224F3BBA42B63EA69EFE971C0101074AEB@misout7msgusr7d.ugd.att.com>
In-Reply-To: <0E3033029745FB4C8BE6F1A3752FAE59E791DF@misout7msgusr7b.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: Ack0P/uBAjEXKO30Q1qnAPoeYbemYQBRZsyA
References: <0E3033029745FB4C8BE6F1A3752FAE59E791DF@misout7msgusr7b.ugd.att.com>
From: "MEDAMANA, JOHN B, ATTOPS" <jmedamana@att.com>
To: l3vpn@ietf.org
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 vote NO.

Need to get agreement on requirements first, before a specific solution
proposal is voted on. I recommend pursuing agreement on requirements in
"draft-mnapierala-part-reqt", which addresses the needs of large
Multicast VPNs. 

John Medamana

AT&T

====================

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