Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt

Benoit Claise <bclaise@cisco.com> Thu, 22 December 2016 13:44 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 423D9129A0C for <l2sm@ietfa.amsl.com>; Thu, 22 Dec 2016 05:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.621
X-Spam-Level:
X-Spam-Status: No, score=-17.621 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=-3.1, 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 AXO0LE91Nsje for <l2sm@ietfa.amsl.com>; Thu, 22 Dec 2016 05:44:36 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ABDC1299FD for <l2sm@ietf.org>; Thu, 22 Dec 2016 05:44:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8552; q=dns/txt; s=iport; t=1482414251; x=1483623851; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=CLa1TOWmy4ZWyipLjkW5PnEHQ5IK0WYSuAh6RTjY2H8=; b=ZWWJm8KbSvcoq9SYvwJILSKC2TasUxTapDRKc10dp+5h9qPoHTAbvaVQ JsFGfgVTvxWJrPf6QkxFyS7mKHzHMc1TRmCHlXsyK7yRFYIZLmcwgQMZA CWYsa6nbqb8DX6EvjBiX4uDs6T+V1eaUmh6ZkAeg3gy4I6JMWluw9G+8x 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AaAQCh11tY/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoLAQEBAQF7L1mNUXKVYI9vhSaCCR8BDIV2AoIqFAECAQEBAQE?= =?us-ascii?q?BAWIohGkCAgIBAWwbCxI0JyIOBgEMBgIBAYhpDqtTLopUAQEBAQEBAQECAQEBA?= =?us-ascii?q?QEBAQEbBYZIggKBWYEIhB0RAYV9BZp5iSBEh1aBdYUHgycjhgyKQId1HzdoHxY?= =?us-ascii?q?NLoViPTQBhjqCLgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.33,388,1477958400"; d="scan'208,217";a="648100849"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Dec 2016 13:44:08 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id uBMDi8ug031784; Thu, 22 Dec 2016 13:44:08 GMT
To: adrian@olddog.co.uk, l2sm@ietf.org, Scott Mansfield <scott.mansfield@ericsson.com>
References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <5b6dbba2-d283-8c81-7aaa-152d05ebdb8c@cisco.com>
Date: Thu, 22 Dec 2016 14:44:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------E939A49732DC794D9650F941"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/qXNFyUF_8djPw7IX4J7ccVuFtLk>
Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt
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: Thu, 22 Dec 2016 13:44:38 -0000

Dear all,

A couple of reflections on L2SM, just before the end of year break.

First, I want to quote one chairs slides 
https://www.ietf.org/proceedings/97/slides/slides-97-l2sm-chairs-slides-01.pdf: 


    We really need this to be driven by Operators
         - Of course, vendors can and should participate
         - But be aware of how the data model is use

I'm always baffled when vendors 'seem to) know better than the operators 
what they need. I don't believe we have spent enough time listening to 
the few operators in the room during the WG meeting.
We have here a group of operators who want to do work in the IETF, and 
we should respect that.

Second, on the differences between IETF and MEF service management.
MEF wants to go for the full LSO architecture (billing, SLA, order 
management, etc.). Perfect.
L2SM charter wants to do something similar to L3SM: a self-contained 
service YANG module.
It would be nice to try to fit the L2SM service models in the MEF LSO 
architecture, but the L2SM work follows a different architectural model 
to LSO, and that there is no value in trying to match the functions 
across model at all costs. This should not invalidate either approach, 
only observe that they are different.

Third, exactly like the L3SM draft, the L2SM draft includes a number of 
technology-specific parameters and these have caused people to claim 
that the I-D must be describing a normalised or configuration model. But 
(of course?) the parameters are needed to configure the CE-PE access 
connections. This is a suitable point of differentiation between MEF and 
L2SM that MEF has worked on CE-based models while L2SM will work on 
PE-based models. Indeed, the IETF works on the networking aspects. 
However, when a building is done somewhere else (typical example, SLA 
management done in MEF), this L2SM YANG module should only contain a 
place holder or a pointer.

Fourth. Discussing those very topics live with Scott Mansfield (our MEF 
- IETF liaison manager) during a workshop recently, we agree that both 
IETF and MEF service models have a place. While we start to see some 
consolidation in terms of YANG modules for device management, we are 
only at the beginning of YANG service modules.

I hope this is useful and that it clarifies the situation.

Regards, Benoit
> Hi,
>
> Our charter mandates that we consider basing our work on
> draft-wen-l2sm-l2vpn-service-model-03.txt
>
> As we discussed in the meeting, that draft is not perfect. But when I asked the
> room whether we thought that it would provide a good starting point that we
> could work with to polish and adapt to become the I-D that we ultimately submit
> for publication as an RFC, I believe I heard a good hum in favour and silence in
> opposition.
>
> So this email starts a formal poll for adoption. Please answer:
>
> Do you think that the WG should adopt draft-wen-l2sm-l2vpn-service-model-03.txt?
>
> If "yes," it would help if you could indicate whether you have read the draft
> and how happy you are with it.
> If "no", it is important that you provide reasons.
>
> This poll will last for two weeks, ending on Saturday 3rd December.
>
> Just to reassure everyone that adoption does not imply that anything is set in
> stone: we expect the WG to continue to develop the content and change whatever
> needs to be changed.
>
> Thanks,
> Adrian and Qin
>
> _______________________________________________
> L2sm mailing list
> L2sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l2sm
> .
>