RE: [L1vpn] Proposed charter for L1VPN WG

"Hamid Ould-Brahim" <hbrahim@nortel.com> Fri, 06 May 2005 13:40 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15375 for <rtg-dir-archive@ietf.org>; Fri, 6 May 2005 09:40:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DU3J6-0005M7-VB for rtg-dir-archive@ietf.org; Fri, 06 May 2005 09:55:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DU33Y-0008Dz-BK; Fri, 06 May 2005 09:39:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DU33W-0008Dr-9P; Fri, 06 May 2005 09:39:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15221; Fri, 6 May 2005 09:39:48 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DU3I0-0005Bz-Hg; Fri, 06 May 2005 09:54:49 -0400
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j46DdSZ12901; Fri, 6 May 2005 09:39:28 -0400 (EDT)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <JJ80V45Z>; Fri, 6 May 2005 09:39:29 -0400
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D0469A24B@zcarhxm0.corp.nortel.com>
From: Hamid Ould-Brahim <hbrahim@nortel.com>
To: Tomonori TAKEDA <takeda.tomonori@lab.ntt.co.jp>, Alex Zinin <zinin@psg.com>
Date: Fri, 06 May 2005 09:39:11 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: rtg-dir@ietf.org, l1vpn@ietf.org
Subject: RE: [L1vpn] Proposed charter for L1VPN WG
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

Tomonori,

> 
> I think framework document can describe service requirements.
> 
> Curret framework document (draft-takeda-l1vpn-framework-03) already 
> contains service requirements. There may be some detailed 
> points to be 
> discussed, especially for the enhanced mode (sig+rtg model), 
> as we see some 
> discussion. (Framework document is describing a broad range 
> of things, but 
> not at the level of protocol requirements.) So, it may be 
> necessary to 
> narrow down the scope for the enhanced mode, which can be 
> done through the 
> mailing list, or if needed, through writing a separate draft. 
> (I don't 
> think we have an immediate need to write a separate draft.)
> 

I do agree the framework draft covers the requirements and is inline 
with ITU L1VPN work. An option that can be considered is to separate 
the requirements from the framework in separate internet draft and 
let the two drafts progress independently (from work point of view).
I assume at certain point solutions (and not the framework) would have 
to be compared to the set of requirements listed.

Hamid.