[L2sm] Re: Proposed Liaison to 3GPP SA5

" Chongfeng " <chongfeng.xie@foxmail.com> Sat, 09 June 2018 07:48 UTC

Return-Path: <chongfeng.xie@foxmail.com>
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 1C462130E28 for <l2sm@ietfa.amsl.com>; Sat, 9 Jun 2018 00:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.019
X-Spam-Level:
X-Spam-Status: No, score=-1.019 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, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.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 ToDT5eEGla0k for <l2sm@ietfa.amsl.com>; Sat, 9 Jun 2018 00:48:31 -0700 (PDT)
Received: from smtpbg303.qq.com (smtpbg303.qq.com [184.105.206.26]) (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 A1C58130E1C for <l2sm@ietf.org>; Sat, 9 Jun 2018 00:48:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1528530506; bh=KuRzFQ0OykWW5f4O7+8ZkagYodkmzQDlr+W79xVn/5Q=; h=From:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Date:Message-ID; b=iim/4IEMVvmM1SI6lhQnV/0X90Okc/JUK7OYfq3MF1vBMpS4paGXF1oI+iEvRnWOX rjtlFEgQ0n0O65YaN89nny9br9+HZl2NRXmUV6euOayIdam3r/Uw5gqLKuCqZjQUMc 1NwBZA0PyHwAPG8x4gTAutJWnlwj1EFwulGjLP8Y=
X-QQ-FEAT: m+dfuO79M2OBw4acAFSqWjmEyFZfWUq75iAEWIBPdbqTaPRgx68f7s3QizHuN T86VRWs2q19mp1GH4nzquslJoJ/fQko5KgLYkQd+7LYiSX+uxd+PhQV5uDXPjgvR+IjRuQq xRYO1RUKO7nYVMjoYtIzsi9sA+em7z4dnOARHSHDP3KhGcuGwI7g/dMdAIr1N46PEvzZtzN TSyel8ohtKslcNTjUhJIzemIoQCoSzJ4T/GnpNvH//xsdHw7buM5OkUnUKO/8brAn6KC/US +bmdgjLlXrgvZH
X-QQ-SSF: 0000000000000060
X-QQ-WAPMAIL: 1
X-QQ-BUSINESS-ORIGIN: 2
X-Originating-IP: 125.33.198.245
X-QQ-STYLE:
X-QQ-mid: wapmail111t1528530503t6087965
From: "=?gb18030?B?Q2hvbmdmZW5n?=" <chongfeng.xie@foxmail.com>
To: "=?gb18030?B?YWRyaWFu?=" <adrian@olddog.co.uk>, "=?gb18030?B?bDJzbQ==?=" <l2sm@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_5B1B8647_0AD74C30_20D91AE2"
Content-Transfer-Encoding: 8Bit
Date: Sat, 9 Jun 2018 15:48:23 +0800
X-Priority: 3
Message-ID: <tencent_68D66C2116BD12AD1027DFFAFA07708DC305@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-QQ-SENDSIZE: 520
X-QQ-FName: F16A343138DE442287D931D8C48B5B90
X-QQ-LocalIP: 10.198.131.167
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/ItMhHAWtyBvEnonmyX4BrhvT1Bs>
Subject: [L2sm] =?gb18030?q?Re=A3=BA_Proposed_Liaison_to_3GPP_SA5?=
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.26
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: Sat, 09 Jun 2018 07:48:38 -0000

Hi, Adrian and Qin, I believe IETF and 3GPP should have more collaboration on network slicing connectivity service standard and YANG data model southbound and northbound work, since YANG data model work has taken off in IETF to meet industry's needs. Therefore I support to send the proposed liaison to 3GPP SA5. Chongfeng------------------ Original ------------------
From: "adrian"<adrian@olddog.co.uk>;
Date: Mon, Jun 4, 2018 07:15 PM
To: "l2sm"<l2sm@ietf.org>;;
Subject: [L2sm] Proposed Liaison to 3GPP SA5


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===

_______________________________________________
L2sm mailing list
L2sm@ietf.org
https://www.ietf.org/mailman/listinfo/l2sm