RE: Advancing the Protocol and Morin Drafts

Renwei Li <renweili@huawei.com> Fri, 03 October 2008 18:53 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 42BB63A6B3A; Fri, 3 Oct 2008 11:53:02 -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 959863A6B3A for <l3vpn@core3.amsl.com>; Fri, 3 Oct 2008 11:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 p2uUZpCEwiuO for <l3vpn@core3.amsl.com>; Fri, 3 Oct 2008 11:52:59 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 600113A69F2 for <l3vpn@ietf.org>; Fri, 3 Oct 2008 11:52:55 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K86000GIF4DAD@szxga01-in.huawei.com> for l3vpn@ietf.org; Sat, 04 Oct 2008 02:53:02 +0800 (CST)
Received: from huawei.com ([172.24.1.12]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K86002MJF4DRO@szxga01-in.huawei.com> for l3vpn@ietf.org; Sat, 04 Oct 2008 02:53:01 +0800 (CST)
Received: from R73802B ([10.51.0.30]) by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K860082CF46A5@szxml05-in.huawei.com> for l3vpn@ietf.org; Sat, 04 Oct 2008 02:53:01 +0800 (CST)
Date: Fri, 03 Oct 2008 11:52:51 -0700
From: Renwei Li <renweili@huawei.com>
Subject: RE: Advancing the Protocol and Morin Drafts
In-reply-to: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
To: 'Marshall Eubanks' <tme@multicasttech.com>, l3vpn@ietf.org
Message-id: <000601c92589$3e8bdaf0$dd758446@china.huawei.com>
Organization: Huawei Technologies
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AckjzrCbVyJuJu5VQe64Xft+lLQqjwBulSNg
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com>
Cc: 'Ross Callon' <rcallon@juniper.net>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: renweili@huawei.com
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 support it...

Renwei


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