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

"" <> Tue, 03 January 2017 14:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F252B1299B0 for <>; Tue, 3 Jan 2017 06:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.841
X-Spam-Status: No, score=-4.841 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id km8iS18HOG3m for <>; Tue, 3 Jan 2017 06:34:03 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 907CD1299B7 for <>; Tue, 3 Jan 2017 06:34:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s201512; t=1483454037; bh=9ThkxZd26fdKCPV4uk6F/+oeuuhmG/MHKOsbln56HGg=; h=Date:From:To:Cc:Subject:References:Mime-Version:Message-ID:Content-Type; b=seM+0r5NIlYH8/hOxMIul1jitmjWryS9tVaCSL3K5Ik8C1VFGuZz5xlUdRRyGKWH8 1QyaYeOt51kAmBL7ghVsmK52WJsTkfyBcYDA47yNwm0UyEd551dVxGBitkbQR0PSVf D76FWo5wG9eEYjGvtzSeahDS++ENf2+aFQLUjK00=
X-QQ-mid: esmtp11t1483454035txmc8c6wg
Received: from Xiechf (unknown []) by (ESMTP) with id ; Tue, 03 Jan 2017 22:33:54 +0800 (CST)
X-QQ-SSF: 0100000000000020FF100000000000B
X-QQ-FEAT: TikaAqnq9r8lE+XyG7ajbzTcJv/L//Oh/vDbbtW59AEgwVhNezxW/HH3MrHeT ZZBME9sy2FnQ+R2tAUwImVRI3ldzMx7bY6Z7GrM5gcLQWqHi/mRa/OlztZRdOTvRSmlzH0S j0ChOe8fB6cWWI9O51hr0iiyDi4FcUw7/iXI4axcylB7fCTei4MUE/wM/L6SibRE9UF9Z+e 702kIETirPafp6LhWtOHfrBGQ1MVVN0X69FNPx3jHshK6zf9aL/DuckLIo10h1lsiaOyqOx ipR2EiQJZBWD0uSr5HPFQipZ/vjapwa0HTr3eGkNRNyUgn
X-QQ-GoodBg: 0
Date: Tue, 3 Jan 2017 22:34:04 +0800
From: "" <>
To: adrian <>, bclaise <>, l2sm <>
References: <0d4501d24132$62ceb590$286c20b0$>, <>, <003001d25fb2$8a84ebb0$9f8ec310$>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 166[cn]
Mime-Version: 1.0
Message-ID: <>
Content-Type: multipart/alternative; boundary="----=_001_NextPart505020173620_=----"
X-QQ-Bgrelay: 1
Archived-At: <>
X-Mailman-Approved-At: Tue, 03 Jan 2017 08:11:43 -0800
Cc: l2sm-chairs <>
Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 03 Jan 2017 14:34:09 -0000

Hi, Adrian,

Firstly, thank you for writing the long mail to illustrate of the status of the l2sm. 
Secondly, I support this draft can be adopted as early as possible. China Telecom is one of the operators who offer L2VPN service, in most cases, in joint with foreign operators. The service model like L2SM will make the service provisioning more flexible and quicker.

Thank you!
From: Adrian Farrel
Date: 2016-12-27 03:59
To: 'Benoit Claise';
CC: l2sm-chairs
Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt
Hi all,
Thanks Benoit for your email and clarifications. Here is my take on where we are and what needs to happen.
[tl;dr -- Adoption poll remains open; please review and comment; authors continue work]
I think we didn't get enough momentum or support for adoption of this document.
At the moment I can't tell whether this resulted from no one caring or from people refraining from commenting after the very strong opposition expressed by David.
Having read and re-read David's email I believe he expresses clearly why he thinks the current draft is not suitable for adoption, and offers two suggestions for alternative approaches, but he neither points at not volunteers for work to support those alternatives.
Therefore, it seems to me that we still only have one draft on the table. We can either work with that draft or give up. I think it would be unfortunate to abandon the working group when we have a number of operators who believe it is a good idea and who have put in a lot of effort. So I would like to see us move forward with what we have and adapt it as necessary. To do that, however, I think the chairs need to hear more voices in support.
I do, however, want to revisit some of the points made in Seoul and by David:
1. This document should not include protocol-specific details.
It is my view that when a PE-mode VPN is being discussed the service offered includes the CE-PE link (access circuit) and the technology details of that link must be represented in the service model.
Clearly when the service is a CE-mode VPN those details don't apply.
In Seoul, we received an offer to go through the current document and flag the protocol parameters that are a concern. I hope that this can be done so that those of us who don't think there is a problem can better understand what the concern is.
2. We should not redevelop work already done by the MEF
I could not agree more, and it seems that the authors of the draft in hand have adopted a similar philosophy intending to point at (or provide containers for) at least QoS, SLA, and billing models developed by the MEF.
On the other hand, attempts to map this service modelling approach into the MEF LSO architecture have not been entirely successful (with lots of differing opinions and some suggestions that parts of multiple LSO reference points are captured in this model). That suggests to me that what is going on in L2SM is closer to a parallel with L3SM than a duplication of MEF work. It may be a different approach or a different thing.
As Benoit said in Seoul (quoting from the minutes) and applying to both of these points:
>   Don't want this WG to do too much. The MEF already
>   working on SLA. This model can point to that. This model tries
>   to be technology agnostic, but if there is some information
>   needed from the customer then it should be in the model.
Bottom line:
- The authors of draft-wen-l2sm-l2vpn-service-model-03.txt should
   continue their work. 
   - Address specific issues raised in Seoul
   - Revisit all protocol-specific parameters to be sure they are needed
   - Adding examples in Section 7 would be most helpful to aid others to 
     see how the model is used
   - Make clearer and more explicit references to use of existing or in-
      progress MEF work.
- The working group should again look at this document and say whether
   it is currently something that we can use for a starting point for our work.
   I would particularly like to hear from network operators (service providers)
   who offer L2VPN services, and from consumers (such as enterprises) who
   purchase such services. As the chairs said in Seoul, this work really needs to
   be led by the operators and not dominated by the vendors.
From: Benoit Claise [] 
Sent: 22 December 2016 13:44
To:;; Scott Mansfield
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 
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 ondraft-wen-l2sm-l2vpn-service-model-03.txt As we discussed in the meeting, that draft is not perfect. But when I asked theroom whether we thought that it would provide a good starting point that wecould work with to polish and adapt to become the I-D that we ultimately submitfor publication as an RFC, I believe I heard a good hum in favour and silence inopposition. 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 draftand 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 instone: we expect the WG to continue to develop the content and change whateverneeds to be changed. Thanks,Adrian and Qin _______________________________________________L2sm mailing listL2sm@ietf.org