Re: [L2sm] Draft liaison response

David Ball <> Mon, 19 December 2016 14:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F0C91129B15 for <>; Mon, 19 Dec 2016 06:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.621
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jOIDtsOI1eAK for <>; Mon, 19 Dec 2016 06:52:58 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 03E66129997 for <>; Mon, 19 Dec 2016 06:52:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=8904; q=dns/txt; s=iport; t=1482159178; x=1483368778; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=s/AkJyXu2RMQw+bSUjfHIrqn2bt3SQPfXo5u4cXTo/k=; b=HUkvktZZgm6kNsxqv4Miu4m/pZdFKLou+vbVEa3elXr1AclSGCoHTv+3 EF+0UL+TvAqNLLw899q1ioazh/YtLILCdnCi5/aAVft9TzO4gHx/NPaXD NGbJmheJCXyU1oYSs2SdZRPL5ccomc9PgoSigOcVEFDc859wam0gZqpsF E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.33,374,1477958400"; d="scan'208,217";a="690569590"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2016 14:52:55 +0000
Received: from [] ( []) by (8.14.5/8.14.5) with ESMTP id uBJEqtq7007149; Mon, 19 Dec 2016 14:52:55 GMT
References: <006901d24d7a$dab3a1c0$901ae540$> <00e001d25a04$b8a6e4c0$29f4ae40$>
From: David Ball <>
Message-ID: <>
Date: Mon, 19 Dec 2016 14:52:55 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <00e001d25a04$b8a6e4c0$29f4ae40$>
Content-Type: multipart/alternative; boundary="------------060436CA4AE6C5B99CE2B98B"
Archived-At: <>
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: Mon, 19 Dec 2016 14:53:00 -0000

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:
> Hi,
> 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
> comments?
> Thanks,
> Adrian
>> Subject: Response to your liaison dated 31st October 2016
>> From: L2SM Chairs
>> To: MEF
>> 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
>> happened.
>> 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