Re: [L2sm] Draft liaison response

顾 戎 <> Thu, 22 December 2016 08:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 78FBC129420 for <>; Thu, 22 Dec 2016 00:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FBCq2otOrMCh for <>; Thu, 22 Dec 2016 00:15:38 -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 694E91293D8 for <>; Thu, 22 Dec 2016 00:15:38 -0800 (PST)
Received: from ([]) by over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Thu, 22 Dec 2016 00:15:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=P4fwzn/0cyl/yRSTmKXjVSgec7cKk0sIyaKS0w0nwz0=; b=Ho9L7dH3xqZ+prZ/492X9emnqxIbrvZte8S26ksQ5AUiwAPJy+R4JDWH/orLQru4/onC+6hkc7zmtmMe6jiqyCaBRGQqMF8QOU+IRXWT4Hutm9SZQdpowdHpLsJ9v4yhV3sqA/WlYFmJagMip5ICzqpy88ftrDd0EuvoFTbyBzT1OXVOnuSZ8F2a/CiEIBV2rhLaRKYkUwphsHQBFtplRFH6Pa1K0CZpOnzRn0P6FLuY1QfdKHc7gx0/dYAcE+RuSMQH1Vny+9Toihukt4BrdzdMG8q7mO8gl/u8aec3KOj59OUNjATwBXycY5lZMROtQzFFZjPJKwbhG4Ube+XNNA==
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.771.7; Thu, 22 Dec 2016 08:15:28 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.789.10 via Frontend Transport; Thu, 22 Dec 2016 08:15:28 +0000
Received: from ([]) by ([]) with mapi id 15.01.0803.013; Thu, 22 Dec 2016 08:15:28 +0000
From: =?gb2312?B?ucsgyNY=?= <>
To: "" <>
Thread-Topic: [L2sm] Draft liaison response
Thread-Index: AQHSXCpm020tf0xIREa7A8MR/pQOzQ==
Date: Thu, 22 Dec 2016 08:15:27 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
x-incomingtopheadermarker: OriginalChecksum:CC0EC0B8D1501B3CFB730F24D909881F8478E7943B6924B43F9E4A2928074D8B; UpperCasedChecksum:6B35AB1F4D663F5EE392EB71491B08B3629E9D89BC5A4EE94AAE991EB31759E9; SizeAsReceived:7305; Count:37
x-tmn: [DLVPKgdjSZvzEkZgdqDxzavIThT0mzfwOirRqUCrXg0=]
x-incomingheadercount: 37
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; PU1APC01HT237; 7:LhXgcsmAO6R9euwVyuwqj3xH+N3nGd+EFqg3Wz7ghqDQoDYKM0Ec/eOqNkQLh71wihvUCEkZIhQPkXXWSgD7LEl1eM5ozIb4yEzyVTgTrLxqNfFuYZ+QWM3fs3lTPFrzOpJnRubFBdz4Ssivc+za6uN8uSj/NGrHr0CiDzXoOAf1VfMAGyQOrjuwGhFTKY88YaHzxUHfcxvEDEJ9Y1QfXkDs8P1njcTwgENyyk+vz1XBGrfVZR94ZdmILE3MESbBLmymXtcq5gt1zcthMgc0KvrlTJoycm8adQ7yZtcfMCXnT4iYBVe/0H9+Z6TGZ56/uc9ZDew6YTLZf7H/DhKCMZX5vEGJX8b3wvpyBRQ8hbISeY8aKtEU2Ru7lYZ89IE7lVFyIgbe9Rk1NQbGQX/1+L20beKS/D46tQovXSm6MfY42GseKfFGEo2b7WKxBlE0KLlhtlB5EZfwff+eejOfAA==
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:PU1APC01HT237;; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: 9f806e11-811d-4d66-958b-08d42a42b05f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(1601124038)(5061506293)(5061507293)(1603103113)(1603101340)(1601125047); SRVR:PU1APC01HT237;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444111334)(444112120)(432015012)(82015046); SRVR:PU1APC01HT237; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT237;
x-forefront-prvs: 01644DCF4A
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HK2PR0201MB165082C9623A0C6665229D4A8B920HK2PR0201MB1650_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Dec 2016 08:15:27.6921 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT237
X-OriginalArrivalTime: 22 Dec 2016 08:15:38.0064 (UTC) FILETIME=[93D3B500:01D25C2B]
Archived-At: <>
Cc: "" <>, "" <>
Subject: Re: [L2sm] Draft liaison response
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: Thu, 22 Dec 2016 08:15:40 -0000

Hi, dear all.
Personally, I think both MEF model and IETF model have their values. However,  they two follow different model design to the best of my knowledge. I'm not sure whether it's suitable to couple MEF model with IETF model.

Actually, I'm much more familar with IETF model such as L2VPN service model and L3VPN service model. So, I would suggest that IETF model can choose to reference MEF relevant specifications. These specification may  be also referenced by MEF model as well. That may be a better way.

Gu Rong

发件人: L2sm [] 代表 David Ball
发送时间: 2016年12月19日 22:53
主题: Re: [L2sm] Draft liaison response

Hi Adrian,

A few comments:

  *   The most relevant part of the MEF work in progress (i.e. the working drafts of their Yang modules) was attached to the liaison rather than being available via the login; so prob need to tweak the wording a bit to thank them for that as well.
  *   Their liaison asked a for a specific clarification with respect to the charter; it would be helpful to provide the clarification  in the reply.
  *   They also suggest that L2SM proceeds by augmenting the MEF modules - it might be useful to address that point specifically in the reply (even if it's only to say that no decision has yet been reached by the WG).


On 19/12/2016 14:32, Adrian Farrel wrote:


As you recall, the MEF sent the IETF a communication on the last day of October


Here is a draft response that Qin and I propose to send as WG chairs. Any




Subject: Response to your liaison dated 31st October 2016

From: L2SM Chairs


Cc: Raghu Ranganathan <><>

    Benoit Claise <><>

    Joel Jaeggli <><>

    L2SM Working Group <><>

    Scott Mansfield <><>

    Mahesh Jethanandani <><>

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. You can see the working group's

charter at

The working group met for the first time at IETF-97 in Seoul 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


Your liaison message is most helpful in pointing out existing and

ongoing MEF work related to the task of the L2SM working group, and the

fact of you making available log-in details for your work-in-progress

is very much appreciated.

The working group has so far been clear in its intent where possible

and consistent with its own work to 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


L2sm mailing list<>


David Ball