[L2sm] FW: L2SM charter proposal

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 26 October 2016 15:13 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 20A541295B6 for <l2sm@ietfa.amsl.com>; Wed, 26 Oct 2016 08:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id y3MbDgeSX7Gk for <l2sm@ietfa.amsl.com>; Wed, 26 Oct 2016 08:13:49 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B56501295A2 for <l2sm@ietf.org>; Wed, 26 Oct 2016 08:13:46 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain []) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u9QFDigA004357 for <l2sm@ietf.org>; Wed, 26 Oct 2016 16:13:44 +0100
Received: from 950129200 ( []) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u9QFDhD5004341 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <l2sm@ietf.org>; Wed, 26 Oct 2016 16:13:44 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l2sm@ietf.org>
References: <201610262137532695733@ctbri.com.cn>
In-Reply-To: <201610262137532695733@ctbri.com.cn>
Date: Wed, 26 Oct 2016 16:13:43 +0100
Message-ID: <063d01d22f9b$8ab12ff0$a0138fd0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_063E_01D22FA3.EC826930"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIWH4Xai9aEDKW8q425LbMHWS4I16Ay978Q
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--17.195-10.0-31-10
X-imss-scan-details: No--17.195-10.0-31-10
X-TMASE-MatchedRID: 5H0h97/a1s4vp9R9KwuJgPDZVqBPJTWp8N9iKSAkgue1eX0jEQ9c6jIe U12C5aCfzjqJngvc26g+nprjbuUrtfH17GX1hHxkaDCzqDR7DPYZKp0SZ4P+dcsIWSRjI55eBpN qUzwLvvcVqN1n3pdLRuaA90At0MqwjxpcxIMfRJRbd1zMnVGjF3B3Uqg8syIULM8X1Jd+PEqjt6 +WJiLXsIXzTWxs0D/dbROt13bZFDjjI7SZVGHDqsFWmsryu9ZfcpgI8ixgsxxGG2hYiBKddJrAS HsnChAHNtrqBJtuOX5BVgr5vOsPONLF6Y0L7R/QcFEiuPxHjsW0X0Yw27VuouQ45nVtPqmx7KBB Z2QBUyxYAerJK6HhgiG6q3sO1y16PisfwAlA31KdCtkMrsOtOg/i8FY2vTOBIDp4740OYDElncP TMo+HsfXTJA26jU4lkhRShy60CjQzG8Dg48sJ/vIVL3+KSNgwkTzAgHG5eNKgJH974mpbq6gTkL gTtTggXql2hIcwl2sTHy/6jlpjHX7qNYdKZkwaFlT/KggLyj0lWygvtTclwPAEgpQDXwIHADRMo ifoBfkzmpYx+UKjh3C2KyYp/H7vWYqLLUX2mAu6kMgL3jbYOtMxD/3e8TxdRtqpRW8sWyKakVWY YDXrTswMS4ODXmCsnuOhtEsGi0ZP5mzaUz6wQBD3+0w1DhqKmRKFhwukYf1kzblkBbANhmAQRn3 L+ljhjSJ3SkiGrFPXkuVVlJMsPZx6Ilif8OzGb/5HBZ6dvRgl3afZehJEWXjQ0NqHYhIhDlnNRf 5gnN8g839dkIFeJEADtkoa9d0A6t1guSoQ4UOeAiCmPx4NwGmRqNBHmBvevqq8s2MNhPB9j2Gwz TE3vXkguuQorcgMxGc0fHRhivO52j+LUF80f27EzoZGOPuR0tTsdQuKqVp+3BndfXUhXQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/imvz0ggNbEvVWCr3Z_Q_zo93O-A>
Subject: [L2sm] FW: L2SM charter proposal
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2016 15:13:53 -0000

Forwarding for ChongFeng who is having list subscription problems.
From: chongfeng.xie@foxmail.com [mailto:1848418658@qq.com] 
Sent: 26 October 2016 14:39
To: l2sm
Cc: adrian; bclaise
Subject: Re: [L2sm] L2SM charter proposal

>> But we could...
>> OLD
>> The working group will coordinate with other working groups responsible for
>> L2VPN protocol work (most notably with BESS and PALS) and with the MEF.
>> NEW
>> The working group will coordinate with other working groups responsible for
>> L2VPN protocol work (most notably with BESS and PALS). It will also
>> with other organizations working on related L2VPN data models (such as the
>> MEF).
>> END
>Noting external dependencies in a separate sentence is better.
>Do the WG proponents plan to share details on how they plan to deal with the
overlapping work in MEF?

Sorry for late reply, talking with our delegate in MEF,I think the collaboration
is needed if the detailed performance parameters, performance metric,
performance objective should be modeled in l2sm model, but the debate point is
how much details we should cover, since I don't believe we should focus on
enumerating a large list of perf measurement related data, if it is healthy to
have them, I think we should create a sla container for placeholder to include
these parameters that are defined by MEF 23.2,definitely MEF reference is
needed, right now we authors still debate on details we should cover.

Chongfeng Xie