[L3sm] Fwd: New Liaison Statement, "Liaison to IETF on IP Services Approved Draft 1"

Benoit Claise <bclaise@cisco.com> Thu, 22 June 2017 12:45 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0548129404 for <l3sm@ietfa.amsl.com>; Thu, 22 Jun 2017 05:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 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, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 LibsgCQHA8RG for <l3sm@ietfa.amsl.com>; Thu, 22 Jun 2017 05:45:55 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 896B11292AE for <l3sm@ietf.org>; Thu, 22 Jun 2017 05:45:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10784; q=dns/txt; s=iport; t=1498135554; x=1499345154; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=Y3iog8YEk77S4T8pc9rvUTCoXMle5Lt8PzHsOnLLL7g=; b=UqVXa3yx8vTzBzYfl8VEXEFtMKUxwloGc7Vtz7MbjNcW1RhB/IUNEz9h uUJwQTQfOi/NMiX8Iryu5WbbvrVL5VPYiGYFwJQdylUXhR49ptDIkpuZc LHsPPFDbYF7Brx/acAS8ggHu1aDYXqACIReHlLUV4zi/G9SEHjxqHcRy+ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BuAQDOuktZ/xbLJq1dGgEBAQECAQEBAQgBAQEBhDqBDYNsihlzkEsiiCyIIoUqghEnhTNKAoM8GAECAQEBAQEBAWsdC4UYAQMBAiNDCxgcAwECFwEBDAYCAiEsAggGDQYCAQGKEAMVEKtsgiYqgyqDXw2EJgEBAQEBAQEBAQEBAQEBAQEBAQEaBYMng0yCCwuCboJXIIITDBwBBYJFgmEFlx2HCzuHM4ZsXIRnggmJE4ZziSWCOm2ISh84gQowIQgbFR+CfIQ/PjYBhx8NF4IZAQEB
X-IronPort-AV: E=Sophos;i="5.39,373,1493683200"; d="scan'208,217";a="653786883"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jun 2017 12:45:52 +0000
Received: from [10.55.221.38] (ams-bclaise-nitro5.cisco.com [10.55.221.38]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v5MCjq4V028678 for <l3sm@ietf.org>; Thu, 22 Jun 2017 12:45:52 GMT
References: <149382509814.21435.13312408514705930156.idtracker@ietfa.amsl.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <149382509814.21435.13312408514705930156.idtracker@ietfa.amsl.com>
Message-ID: <8e4d5b55-7641-b024-4737-14c48de20b7d@cisco.com>
Date: Thu, 22 Jun 2017 14:45:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <149382509814.21435.13312408514705930156.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------A0273E9BBEEAA8CAB0FE20A5"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/D7BHyx_HDwb6jb5iG4GqaUocE1k>
Subject: [L3sm] Fwd: New Liaison Statement, "Liaison to IETF on IP Services Approved Draft 1"
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2017 12:45:58 -0000

FYI.

Regards,B.


-------- Forwarded Message --------
Subject: 	New Liaison Statement, "Liaison to IETF on IP Services 
Approved Draft 1"
Date: 	Wed, 3 May 2017 08:24:58 -0700
From: 	Liaison Statement Management Tool <lsmt@ietf.org>
To: 	Benoit Claise <bclaise@cisco.com>, Alvaro Retana 
<aretana@cisco.com>, Alia Atlas <akatlas@gmail.com>, Deborah Brungard 
<db3546@att.com>, Warren Kumari <warren@kumari.net>
CC: 	Alvaro Retana <aretana@cisco.com>, Deborah Brungard 
<db3546@att.com>, nan@mef.net, Alia Atlas <akatlas@gmail.com>, Warren 
Kumari <warren@kumari.net>, The IETF Chair <chair@ietf.org>, 
ssteiff@pccwglobal.com, rraghu@ciena.com, Benoit Claise 
<bclaise@cisco.com>, Raghu Ranganathan <rraghu@ciena.com>



Title: Liaison to IETF on IP Services Approved Draft 1
Submission Date: 2017-05-03
URL of the IETF Web page: https://datatracker.ietf.org/liaison/1521/

From: Raghu Ranganathan <rraghu@ciena.com>
To: Warren Kumari <warren@kumari.net>,Benoit Claise <bclaise@cisco.com>,Alia Atlas <akatlas@gmail.com>,Alvaro Retana <aretana@cisco.com>,Deborah Brungard <db3546@att.com>
Cc: Alvaro Retana <aretana@cisco.com>,Deborah Brungard <db3546@att.com>,Alia Atlas <akatlas@gmail.com>,Warren Kumari <warren@kumari.net>,The IETF Chair <chair@ietf.org>,Benoit Claise <bclaise@cisco.com>,Raghu Ranganathan <rraghu@ciena.com>
Response Contacts: rraghu@ciena.com, nan@mef.net, ssteiff@pccwglobal.com
Technical Contacts:
Purpose: For information

Body: Following our previous liaisons, we would like to update you on the progress of the MEF IP Service Attributes project. A new Approved Draft of our specification for IP Service Attributes for Subscriber Services is available, which can be accessed as described below. Note that a corresponding specification for IP Service Attributes for Operator Services is in progress but an Approved Draft is not yet available.

In the course of our work, we have reviewed some of the internet drafts from the L3SM working group that preceded publication of RFC 8049 ("Yang Data Model for L3VPN Service Delivery"), and we used this as input to our specification. Now that RFC 8049 is published, we intend to review it again to ensure our work remains aligned. We would appreciate your review of our Approved Draft, and in particular any assistance you can give in identifying areas where it may conflict or be otherwise misaligned with RFC 8049.

Note that the scope of the current IP Service Attributes project does not include definition of a yang module; however, we expect that a future project will include specification of a yang module based on the service attributes defined in this document. It is our hope that such a module can be defined as an augment of the module defined in RFC 8049.

MEF’s liaison partners may access all MEF approved drafts as follows:
https://mef.net/liaison-login
Username: mef
Password: M3F3030

The next MEF meetings are:
July 24 - 27, Toronto, Canada
October 23 - 26, Raleigh, USA
Attachments:

     L00263_001_LiaisontoIETFonIPServicesApprovedDraft1_Ball_Ranganathan.pdf
     https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2017-05-03-mef-ops-rtg-liaison-to-ietf-on-ip-services-approved-draft-1-attachment-1.pdf

.