Re: Advancing the Protocol and Morin Drafts

ycai <ycai@cisco.com> Wed, 22 October 2008 04: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 BCE423A688C; Tue, 21 Oct 2008 21:07:15 -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 2202A3A63EC for <l3vpn@core3.amsl.com>; Tue, 21 Oct 2008 21:07:15 -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 GGvxtV1dRNaH for <l3vpn@core3.amsl.com>; Tue, 21 Oct 2008 21:07:14 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 37A893A688C for <l3vpn@ietf.org>; Tue, 21 Oct 2008 21:07:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,461,1220227200"; d="scan'208";a="180091695"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 22 Oct 2008 04:08:01 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9M481Wl027919; Tue, 21 Oct 2008 21:08:01 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9M4815N022333; Wed, 22 Oct 2008 04:08:01 GMT
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Oct 2008 21:08:01 -0700
Received: from 10.21.79.59 ([10.21.79.59]) by xmb-sjc-216.amer.cisco.com ([171.70.151.184]) with Microsoft Exchange Server HTTP-DAV ; Wed, 22 Oct 2008 04:07:49 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Tue, 21 Oct 2008 21:07:48 -0700
Subject: Re: Advancing the Protocol and Morin Drafts
From: ycai <ycai@cisco.com>
To: Marshall Eubanks <tme@multicasttech.com>, l3vpn@ietf.org
Message-ID: <C523F524.4DF32%ycai@cisco.com>
Thread-Topic: Advancing the Protocol and Morin Drafts
Thread-Index: Ackz+75X6d02wUmDSUyr7AiQtQwBkw==
In-Reply-To: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 22 Oct 2008 04:08:01.0382 (UTC) FILETIME=[C651B060:01C933FB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1297; t=1224648481; x=1225512481; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ycai@cisco.com; z=From:=20ycai=20<ycai@cisco.com> |Subject:=20Re=3A=20Advancing=20the=20Protocol=20and=20Mori n=20Drafts=20 |Sender:=20; bh=QVFtIrsxM2E+0eLrRHcoceKR3hMMqsrYY/DDyr8c0pE=; b=Imb+2Sf6rHVLag+1LPgbG27O2pksGPOEZYkg3sfm8vVYOoNvX3HsJk2ZLP V5ipICSWjMZfo4gMRT8hhs5rcrKdhnHK/gH1KjrTtJl6NJ+VrVc5itQBqvrK pKW88oey68;
Authentication-Results: sj-dkim-2; header.From=ycai@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
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

Marshall,  Danny,


On 10/1/08 7:04 AM, "Marshall Eubanks" <tme@multicasttech.com> wrote:

> 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

No.

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

Given where the two solution drafts are,  I'm not sure we need another
requirement draft. 

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

I think these two drafts can progress without 1) or 2) above.

Thanks.


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


-- 
Yiqun