[L2sm] Proposed Liaison to 3GPP SA5

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 04 June 2018 11:15 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD0E126C89 for <l2sm@ietfa.amsl.com>; Mon, 4 Jun 2018 04:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 5-FSzekx5dFD for <l2sm@ietfa.amsl.com>; Mon, 4 Jun 2018 04:15:32 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EBFE126CD6 for <l2sm@ietf.org>; Mon, 4 Jun 2018 04:15:32 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id w54BFT8x004005 for <l2sm@ietf.org>; Mon, 4 Jun 2018 12:15:30 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0F8F222052 for <l2sm@ietf.org>; Mon, 4 Jun 2018 12:15:27 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id EE0BC2204A for <l2sm@ietf.org>; Mon, 4 Jun 2018 12:15:26 +0100 (BST)
Received: from 950129200 (243.125.113.87.dyn.plus.net [87.113.125.243]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id w54BFPWl014102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <l2sm@ietf.org>; Mon, 4 Jun 2018 12:15:26 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l2sm@ietf.org>
References:
In-Reply-To:
Date: Mon, 4 Jun 2018 12:15:24 +0100
Message-ID: <000901d3fbf5$5648d790$02da86b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdP77mZy+ziBQucgTuOCdr0I0+8PugABou9A
Content-Language: en-gb
X-Originating-IP: 87.113.125.243
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-23886.006
X-TM-AS-Result: No--3.465-10.0-31-10
X-imss-scan-details: No--3.465-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23886.006
X-TMASE-Result: 10--3.465400-10.000000
X-TMASE-MatchedRID: hit9y+tO4pAMCLEGW7c2cMK1Ib9JAALxcJrLR4rumDmX5kFNcJkaaoL8 17LE9TTsEBLBADfD9LpqqbO4nn79RWCOYHRIPhtPU+OjsPhIWDgWTveLitVUgQYrZlX3QccS3/+ Vf+IwaAAhQB950aZZPe5MXQFHmFAZ2v02uJpYZ8NT5IIGQvvzfhkqnRJng/51OiWn1ehFOG9XGf IJMGgUBOS66uRr1w3bLQ1gU0kQBv+NfvSCeaA1PISSxX6w03pu+oCP/ssLgo9nlJ9Df1nJSXwsT 5jF3WC+o77Bv4Es9Tvo/Kry0qRHJzpI0A0aNTmUngIgpj8eDcBZDL1gLmoa/OYq7Exe0AIo32mP O5tnascnRE+fI6etkhvUP5vnK+dU9AisDMfXHh6sbRreEJyZVt0nh5YMSSwvBvtT1D69s8BiiXn 3sXdwzc2TL8qdRQkLaxhGfiSq8uXdOuTfOG9SF03+9BzFCkVzNAW83zYDw/v1OlCIPxKfizngMR AgrdeEyfkWaeG5p9A=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/S-fbUu8x1Rhoq_tFDTFHoMxmIDA>
Subject: [L2sm] Proposed Liaison to 3GPP SA5
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2018 11:15:35 -0000

Hi WG,

3GPP SA5 is working on Management and orchestration of 5G networks and network slicing (http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G) and is considering various existing data models as references. 3GPP Release-15 is targeting freeze date of September 2018 and plan two meetings in June and August respectively to meet the deadline of 3GPP Release-15.
 
They seem to have been soliciting input from various SDOs (most recently the BBF) but have not approached the IETF. This may be because they already know what we are working on, or it may be because they didn't realise.

So Qin and I propose to send the following liaison statement to them for information. Since the next meeting is on June 26th, we think the deadline for sending this is should be June 15th.

Any comments or edits would be welcomed.

Thanks for any input or advice.

Qin and Adrian

=== Draft LS ===

To: 3GPP SA5
Cc: Thomas Tovinger, 3GPP SA5 Chairman
       Ignas Bagdonas and Warren Kumari, IETF Operations and Management ADs
From: Qin Wu and Adrian Farrel, IETF L2SM working group co-chairs
For: Information

We note that 3GPP SA5 is working on Management and orchestration of 5G networks and network slicing (http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G) and is considering various existing data models as references. 3GPP Release-15 is targeting freeze date of September 2018 and plan two meetings in June and August respectively to meet the deadline of 3GPP Release-15. We would like to take this opportunity to inform you of the status of several pieces of work in the IETF that satisfy the transport support for network slicing on IP services , L2 service, and TE service.

RFC 8299 provides A YANG Data Model for L3VPN Service Delivery.
This document is a published RFC with IETF consensus.
https://www.rfc-editor.org/rfc/rfc8299.txt
 
draft-ietf-l2sm-l2vpn-service-model provides A YANG Data Model for L2VPN
Service Delivery.
This document has achieved working group and IETF consensus, and is currently completing approval for publication as an RFC.
https://www.ietf.org/id/draft-ietf-l2sm-l2vpn-service-model-10.txt
 
RFC 8309 sets the previous two documents in context by explaining what the IETF means by the term "Service Model"
https://www.rfc-editor.org/rfc/rfc8309.txt
 
You may also be interested in work in the TEAS working group on Abstraction and Control of Traffic Engineered networks (ACTN).
In particular, there is YANG model for Virtual Network operation in an ACTN context that may be of specific interest to you:
https://www.ietf.org/id/draft-ietf-teas-actn-vn-yang-00.txt
 
Wishing you all success in your work,
Qin Wu and Adrian Farrel
Co-chairs, IETF L2SM working group
===END===