Re: [L2sm] New Liaison Statement, "Response to your liaison dated 31st October 2016"

"Ranganathan, Raghu" <> Tue, 27 December 2016 18:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 58FCA1296B2 for <>; Tue, 27 Dec 2016 10:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 8MGNY-g86Ro2 for <>; Tue, 27 Dec 2016 10:29:08 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5F33A12948C for <>; Tue, 27 Dec 2016 10:29:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-ciena-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=sfl/LYpLpVu6hYXRL5rMr+rSjfurHxwK0taR8G1/OCk=; b=PZfQo3Cw55zc6vLoA0YcfL7BewXkqV5rTfjIRK7SzqZD9Yf4yUQBJCcLiazc2PHVkuKah8KFVraUmheNWfeUKrGVxFa0Y4rtmMeWi4UACyk9UmpHfAUa425zYPoh8VIOncBhxlGDNKcHcJDtPYsPiRFNJh/Bob6hphiABdlyTn4=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.803.11; Tue, 27 Dec 2016 18:29:05 +0000
Received: from ([]) by ([]) with mapi id 15.01.0803.021; Tue, 27 Dec 2016 18:29:05 +0000
From: "Ranganathan, Raghu" <>
To: Liaison Statement Management Tool <>
Thread-Topic: New Liaison Statement, "Response to your liaison dated 31st October 2016"
Thread-Index: AQHSYB8OVBLFDiJ7QEi17dz8r8urBaEcHfcj
Date: Tue, 27 Dec 2016 18:29:05 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-ms-office365-filtering-correlation-id: d60c7c21-cb1b-4c46-5c6e-08d42e863d8e
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:MWHPR04MB0383;
x-microsoft-exchange-diagnostics: 1; MWHPR04MB0383; 7:gzXMvqhOJQNRmsb9fXh6bDaDBHcwBbmlYMr3jAN4eP3mbGTR7+L40LEvli/AWIafuAeKXAb0eszNILisA1SmgzJgsSfjtIe5qc6Om8y8e+ek38aocX/Kn0qYKniTqorB00AjFNgxqfqXX37m0hZv5AIAaSNDTSpv6Kwek++/9SuT4OHDaedMe0robAqzY0kzZ+6sUKUoDxEcQVF/YftKAjVMv1JOZk3XRHYOnOREDKluw7iUREcVcammz7ptVOIYi8mRFVuZllwXlm58Csn3URhaDTqpmoUf8lw1/neCffB5hdHIqHhQEZvYg+kPe4e/xGnGGO0y83AEddrSXUHXWjFMiLQyvxRyTtN9O+WE5GT1WU8DAwZJwCeVMSIMGXwIXhkcjEFp14jFFm2Z2SiBhavWKCpaIjvgOF4VyVWNMqcErOihfobEG5sdD5LLgxTUMHX6moo6IJOUXtYVWA3OjQ==
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123555025)(20161123560025)(20161123558021)(20161123564025)(20161123562025)(6072148); SRVR:MWHPR04MB0383; BCL:0; PCL:0; RULEID:; SRVR:MWHPR04MB0383;
x-forefront-prvs: 0169092318
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(377424004)(377454003)(199003)(189002)(81156014)(189998001)(81166006)(8676002)(4001150100001)(97736004)(66066001)(5890100001)(50986999)(101416001)(76176999)(54356999)(99286002)(305945005)(106116001)(106356001)(31430400001)(105586002)(5660300001)(68736007)(92566002)(6116002)(102836003)(3846002)(76576001)(38730400001)(2906002)(25786008)(7736002)(6436002)(4326007)(9686002)(6916009)(345774005)(6506006)(77096006)(122556002)(8936002)(74316002)(2900100001)(229853002)(3660700001)(7696004)(86362001)(33656002)(3280700002)(110136003)(2950100002); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR04MB0383;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR04MB03853ECB0712E2D13E8BBD6FCE690MWHPR04MB0385namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Dec 2016 18:29:05.6985 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 457a2b01-0019-42ba-a449-45f99e96b60a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR04MB0383
Archived-At: <>
Cc: "" <>, Mahesh Jethanandani <>, L2VPN Service Model Discussion List <>, Scott Mansfield <>, Joel Jaeggli <>, Benoit Claise <>, Adrian Farrel <>, Qin Wu <>
Subject: Re: [L2sm] New Liaison Statement, "Response to your liaison dated 31st October 2016"
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, 27 Dec 2016 18:29:11 -0000

Hello Qin Wu and Adrian,
Thanks. I will post it to the attention of our Members.

--Raghu (Sent from Phone)

From: Liaison Statement Management Tool
Sent: Tuesday, December 27, 2:56 AM
Subject: New Liaison Statement, "Response to your liaison dated 31st October 2016"
To: Ranganathan, Raghu
Cc: Ranganathan, Raghu, Mahesh Jethanandani, Scott Mansfield, L2VPN Service Model Discussion List, Benoit Claise, Joel Jaeggli, Adrian Farrel, Qin Wu, Adrian Farrel

Title: Response to your liaison dated 31st October 2016 Submission Date: 2016-12-26 URL of the IETF Web page: From: "Adrian Farrel" To: Cc: Joel Jaeggli ,Adrian Farrel ,Benoit Claise ,Qin Wu ,Raghu Ranganathan ,L2VPN Service Model Discussion List ,Scott Mansfield ,Mahesh Jethanandani ,, Response Contacts: Adrian Farrel ,Qin Wu Technical Contacts: Purpose: In response Referenced liaison: Liaison to IETF on proposed Working Group on L2SM ( Body: Thank you for your liaison message of 31st October this year addressed to the IESG and OPS Area Directors. Since your liaison, the Layer 2 VPN Service Model (L2SM) working group has been formed by the IESG. This happened right after the L3SM working group succeeded in its goal of describing an L3VPN service as a data model by documenting it in the YANG modeling language. You can see the new working group's charter at and the product of the L3SM working group at The L2SM working group met for the first time at IETF-97 in Seoul during November and had a lively discussion about its work including the issues of terminology, functional boundaries, and potential overlap with or use of MEF work. You can see the meeting materials and draft minutes at by searching for "L2SM". Both Mahesh Jethanandani and Scott Mansfield were in the room during the meeting and can probably give you their views on what happened. L2SM will follow the same path as was taken for L3SM, and is tasked to do something similar to L3SM. Your liaison message is most helpful in pointing out and supplying copies of existing and on-going MEF work related to the task of the L2SM working group, and the fact of you making available log-in details and material for your work-in-progress is very much appreciated. You asked a specific question in your communication: > Is the focus of L2SM about the internal network technologies and > implementations as opposed to "characteristics of the service as > discussed between the operators and their customers"? The answer is the latter (although it should be noted that there is some debate about whether "operator" or "service provider" is the correct term). Through the discussion during the meeting and on the list, we believe a suitable point of differentiation between MEF and L2SM is that MEF has worked on CE-based models while L2SM will work on PE-based models. PE-based models necessarily include a number of technology-specific details and will focus on the networking aspects of the service while still keeping the realisation of the service within the provider's network as technology agnostic. Furthermore, while the MEF clearly embraces all aspects of the LSO architecture including billing, SLA, order management, life-cycle management, etc, the L2SM working group is tasked to do something much smaller: a self-contained service YANG module similar to tat produced for L3SM. While it would be nice to fit the L2SM work into the MEF LSO architecture, it appears that L2SM follows a different architectural approach, and that there is no value in trying to "fit a square peg in a round hole" by trying to force a match of the functions across the two approaches. This does not invalidate either approach, but only observes that they are different. The working group has so far been clear in its intent to, where possible and consistent with its own work, re-use by reference any relevant existing material such as that developed by the MEF Forum. So far it has identified SLAs, QoS, and Billing as components that may very well be candidates for such re-use. At the moment, the working group is at a very early stage. We welcome participation by all interested parties, but in particular by service providers and service customers since they are the principal users of the YANG model under construction. Participation is open to all via the mailing list We wish you well with your January meeting. Qin Wu and Adrian Farrel L2SM Working Group Chairs Attachments: No document has been attached