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

Scott Mansfield <scott.mansfield@ericsson.com> Tue, 03 January 2017 19:19 UTC

Return-Path: <scott.mansfield@ericsson.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 5F82F129B04 for <l2sm@ietfa.amsl.com>; Tue, 3 Jan 2017 11:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level:
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
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 uq0cUAiFOmmv for <l2sm@ietfa.amsl.com>; Tue, 3 Jan 2017 11:19:22 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494D5129AE5 for <l2sm@ietf.org>; Tue, 3 Jan 2017 11:19:21 -0800 (PST)
X-AuditID: c6180641-e87ff70000000a0b-dd-586ba4cc4a31
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by (Symantec Mail Security) with SMTP id E1.F2.02571.CC4AB685; Tue, 3 Jan 2017 14:19:10 +0100 (CET)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0319.002; Tue, 3 Jan 2017 14:19:18 -0500
From: Scott Mansfield <scott.mansfield@ericsson.com>
To: Benoit Claise <bclaise@cisco.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "l2sm@ietf.org" <l2sm@ietf.org>
Thread-Topic: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt
Thread-Index: AQHSXFl6C4zNlwTvBUSSUw5sf+rGa6EnMKWA
Date: Tue, 3 Jan 2017 19:19:18 +0000
Message-ID: <EF35EE4B92789843B1DECBC0E24558644C65254F@eusaamb105.ericsson.se>
References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> <5b6dbba2-d283-8c81-7aaa-152d05ebdb8c@cisco.com>
In-Reply-To: <5b6dbba2-d283-8c81-7aaa-152d05ebdb8c@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.12]
Content-Type: multipart/alternative; boundary="_000_EF35EE4B92789843B1DECBC0E24558644C65254Feusaamb105erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZXLrHW/fckuwIg8f7bSx+9Nxgtjj6WMLi zsuXjA7MHlN+b2T1WLLkJ5PHis0rGQOYo7hsUlJzMstSi/TtErgy5p86y1iwuqSic/5ilgbG e0ldjJwcEgImEvu7TzJ3MXJxCAmsZ5Ro6+uAcpYxSjT9b2QHqWIDqtq6azojiC0iUCqx78Be ZhBbWCBQYt2fz0BxDqB4kMSNO3IQJUYS5xdfAmtlEVCROLF4ERuIzSvgK7Hy+ClWkHIhgVyJ Z3MzQUxOAVuJr4u9QCoYBcQkvp9awwRiMwuIS9x6Mp8J4kwBiSV7zjND2KISLx//Y4WwlSTm vL7GDFGfL7G/8Sw7xCZBiZMzn7BMYBSehWTULCRls5CUQcR1JBbs/sQGYWtLLFv4mhnGPnPg MROy+AJG9lWMHKXFBTm56UaGmxiBMXNMgs1xB+PeXs9DjAIcjEo8vAYt2RFCrIllxZW5hxgl OJiVRHjjvgCFeFMSK6tSi/Lji0pzUosPMUpzsCiJ814PuR8uJJCeWJKanZpakFoEk2Xi4JRq YFQQKN2xR/WF+Unevadu5FprZUWGcZrdeVYl8/ZMwMeVs8oLNpw2CW/vOZ9y8vIC+a87Sy7y pDVL+S/7tuu3Tf1zI24twQU1jY3K2/+zGu5Qcjksznfg+nXGZIvpE7u/5k2YFvx7dddsQ/3Q MLXa9zPd048pvX8d89NniUZABeeFTdyL+0wnliuxFGckGmoxFxUnAgCLqa2GlQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/k8RGGJcKf4tCVzkWX9HttYEB_mI>
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: Tue, 03 Jan 2017 19:19:24 -0000

I agree with Benoit.  There are many dimensions to the modeling space and we can't let the perfect be the enemy of the good.  Constant communication and sharing will help alignment while allowing the people that actually run networks to get what they need.  30+ years of object-oriented software development (should have) taught all designers/architects/programmers that the first iteration of a solution is not the best and most optimized.  Each iteration provides the opportunity to abstract, refine, refactor, and extend.  Proper information hiding and encapsulation is key.  Automation is very important and we need to work together to ensure that whatever models that are created are supported by tools that allow for effective reuse and extensions.

Regards,
-scott.

From: Benoit Claise [mailto:bclaise@cisco.com]
Sent: Thursday, December 22, 2016 8:44 AM
To: adrian@olddog.co.uk; l2sm@ietf.org; Scott Mansfield <scott.mansfield@ericsson.com>
Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt

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:<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<mailto:L2sm@ietf.org>

https://www.ietf.org/mailman/listinfo/l2sm

.