IETF Logo Mail Archive

Re: VPMS Requirements as WG Doc?

cao wei <caowayne@huawei.com> Fri, 21 November 2008 05:32 UTC

Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 110263A6A5A; Thu, 20 Nov 2008 21:32:34 -0800 (PST)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 887003A6A5A for <l2vpn@core3.amsl.com>; Thu, 20 Nov 2008 21:32:32 -0800 (PST)
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 zIo6bn-ZEJmV for <l2vpn@core3.amsl.com>; Thu, 20 Nov 2008 21:32:31 -0800 (PST)
Received: from lhrga01-in.huawei.com (lhrga01-in.huawei.com [195.33.106.110]) by core3.amsl.com (Postfix) with ESMTP id B3CB43A6827 for <l2vpn@ietf.org>; Thu, 20 Nov 2008 21:32:31 -0800 (PST)
Received: from huawei.com (lhrml01-in [172.18.7.5]) by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KAO00J7E4Q3VO@lhrga01-in.huawei.com> for l2vpn@ietf.org; Fri, 21 Nov 2008 05:32:27 +0000 (GMT)
Received: from home ([130.129.78.211]) by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KAO00DJD4Q0W6@lhrga01-in.huawei.com> for l2vpn@ietf.org; Fri, 21 Nov 2008 05:32:27 +0000 (GMT)
Date: Fri, 21 Nov 2008 13:32:24 +0800
From: cao wei <caowayne@huawei.com>
Subject: Re: VPMS Requirements as WG Doc?
To: Shane Amante <shane@castlepoint.net>, l2vpn@ietf.org
Message-id: <7136B8BACD164DF4B24C51E938F421CB@home>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <D8D349FE-F57C-40BE-A888-D6BE4C9C111C@castlepoint.net>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

1. Support it to be WG document
----- Original Message ----- 
From: "Shane Amante" <shane@castlepoint.net>
To: <l2vpn@ietf.org>
Sent: Friday, November 21, 2008 9:41 AM
Subject: VPMS Requirements as WG Doc?


> Hi all,
> 
> At this morning's L2VPN WG meeting, Yuji presented the latest updates  
> and changes on the VPMS requirements draft:
> http://tools.ietf.org/html/draft-kamite-l2vpn-vpms-frmwk-requirements-02
> 
> We would now like to poll the WG mailing list and ask two questions:
> 1)  Is there support for making this a WG document?
> 2)  Are there WG members who support making this a WG document that  
> will volunteer to be reviewers as the doc progresses through WG  
> reviews, WG Last Call, etc.?
> 
> Thanks,
> 
> -shane & Vach

v2.23.0 | Report a Bug | By Email