Re: [L2sm] L2SM charter proposal

Benoit Claise <bclaise@cisco.com> Wed, 02 November 2016 17:19 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B941294A3 for <l2sm@ietfa.amsl.com>; Wed, 2 Nov 2016 10:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Level:
X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUfpXQ3HnStc for <l2sm@ietfa.amsl.com>; Wed, 2 Nov 2016 10:19:54 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 006E512941D for <l2sm@ietf.org>; Wed, 2 Nov 2016 10:19:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5534; q=dns/txt; s=iport; t=1478107194; x=1479316794; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=4PvWUjIJXOBUbHMCuj+Ep1VDQ46l0PYm3BcfElV3Xdw=; b=EpsgX6pB6PNPUTnNiXm+QLRVDa4ELm+Kyek4jk/wt+UJv1ckQSLSJSFX UaptyawHYbourV+Pxvgwh1IE0NREbqZwW2H5apRIqJ1H+RPO7yyt6WQOy 4cLXrTMXBBQ7sC+3xKDEoQATdVhOZ60pNd2x+2ED+zhhNs7dUw5Fwe50O E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BYAgBBHxpY/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgnM5AQEBAQGBIY4JlwGPMIUXggeGIgKCYxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?iAQEDAXkQC0ZXBAIBDAgBAYhKCLpFAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIY9g?= =?us-ascii?q?X2CWIonBYhJkVSQOol1hhSJP4ddHjZWCAmEWj49iRABAQE?=
X-IronPort-AV: E=Sophos;i="5.31,583,1473120000"; d="scan'208,217";a="649640465"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Nov 2016 17:19:52 +0000
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id uA2HJp53002794; Wed, 2 Nov 2016 17:19:51 GMT
To: "chongfeng.xie@foxmail.com" <1848418658@qq.com>, l2sm <l2sm@ietf.org>
References: <201610262137532695733@ctbri.com.cn>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <014a8020-1e65-a77a-47af-357c4fd22710@cisco.com>
Date: Wed, 2 Nov 2016 18:19:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <201610262137532695733@ctbri.com.cn>
Content-Type: multipart/alternative; boundary="------------E97C5A0FCBE4FAE23E5B6F15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/IaZQChw-JB1ZQUMT82b_2g7MfGI>
Cc: adrian <adrian@olddog.co.uk>
Subject: Re: [L2sm] L2SM charter proposal
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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, 02 Nov 2016 17:19:55 -0000

Hi Chongfeng,

Which organizations are working on related L2VPN data models, other than 
MEF?

Regards, Benoit
>
>
>
> >> 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 coordinate
> >> 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*
>
> ------------------------------------------------------------------------
>