[L2sm] 答复: Re: Proposed Liaison to 3GPP SA5

顾 戎 <gurong_cmcc@outlook.com> Thu, 14 June 2018 05:12 UTC

Return-Path: <gurong_cmcc@outlook.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 CF7D3131093 for <l2sm@ietfa.amsl.com>; Wed, 13 Jun 2018 22:12:42 -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 (2048-bit key) header.d=outlook.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 S2YyfS2G-0jR for <l2sm@ietfa.amsl.com>; Wed, 13 Jun 2018 22:12:39 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255068.outbound.protection.outlook.com [40.92.255.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2841131090 for <l2sm@ietf.org>; Wed, 13 Jun 2018 22:12:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fPiRezcI2aghfWa76qhlW6zG+bzoUZTvU0D33+W7XIY=; b=kZtXmoW86HNq5kM/kgRON3ZS9RqG6cljPvLo+V0EnZ18Dh6d1mGEeFxeqdJOV88RX5HrL/2vTIyLs8vGviYgnqh9vhEbBWSq6fQFgYvr8Thbch3v7yUWg8TK4++2vBn5802WoPllXfi281sPv66Zjlww3hJloIpnVLhMaRgcnVJumlk5NvcxWJE5BLwF5otR1rnujVcEpfm+bVDuRnmCvwb/q/ca00bvaXKCUMFXDa4wnN+fbZV4PIYq2eUMZHjuwLlxuxrhH7i6XPoq83chPhzYeAtG7pdCu1aK/V8jjVhIBSupNxDODvABY2hOTP7GINGNT7yPq8jKMhIT6zdM9g==
Received: from SG2APC01FT133.eop-APC01.prod.protection.outlook.com (10.152.250.58) by SG2APC01HT121.eop-APC01.prod.protection.outlook.com (10.152.251.206) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.863.11; Thu, 14 Jun 2018 05:12:33 +0000
Received: from HK2PR02MB1251.apcprd02.prod.outlook.com (10.152.250.53) by SG2APC01FT133.mail.protection.outlook.com (10.152.250.191) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.863.11 via Frontend Transport; Thu, 14 Jun 2018 05:12:33 +0000
Received: from HK2PR02MB1251.apcprd02.prod.outlook.com ([fe80::2d21:34ab:4c4d:ed8f]) by HK2PR02MB1251.apcprd02.prod.outlook.com ([fe80::2d21:34ab:4c4d:ed8f%4]) with mapi id 15.20.0863.016; Thu, 14 Jun 2018 05:12:33 +0000
From: =?gb2312?B?ucsgyNY=?= <gurong_cmcc@outlook.com>
To: adrian <adrian@olddog.co.uk>, l2sm <l2sm@ietf.org>
Thread-Topic: =?gb2312?B?W0wyc21dIFJlo7ogUHJvcG9zZWQgTGlhaXNvbiB0byAzR1BQIFNBNQ==?=
Thread-Index: AQHT/8ZKXyx4gghS4UWIPhz/sUock6RfO+3Y
Date: Thu, 14 Jun 2018 05:12:33 +0000
Message-ID: <HK2PR02MB12512D4661A80A5FE03EEB148B7D0@HK2PR02MB1251.apcprd02.prod.outlook.com>
References: <tencent_68D66C2116BD12AD1027DFFAFA07708DC305@qq.com>
In-Reply-To: <tencent_68D66C2116BD12AD1027DFFAFA07708DC305@qq.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:69BFED9A493C40A6970F9717736C056CF5C51AF281CC84C19480C33CB7BB9B5D; UpperCasedChecksum:E3E463E1BE255B768432E79C1323547B06EAE1C99137BCF3FC0F8D3E029D09DF; SizeAsReceived:7059; Count:45
x-tmn: [3TS2VtzhK0po5A6sT99Mb4uzw7etkm0Z]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT121; 7:CV8Sp5JfRo9QMtbHytGL3Lkr2ZH42BtczWMguby3ashycnKLicdamm3I0zXTnORa4AYB3ct0PhJ7j+atpABMAizxWOBLQHbXmcFqMs5vnnLeXqaRdED4Wn6B+L4DIY1QRERi91nSyCptzgFAi9LBdp5DWgGi41RFqIMvzYsFqMvrMadk9qsr45zlMeJYstZ/dIrrQ9R6oo70R743EuBe8xMY5EnGvYnZvOpVPw5je62TRXQZCJWG7r9xhzQDPg5L
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125500)(1603101448)(1701031045); SRVR:SG2APC01HT121;
x-ms-traffictypediagnostic: SG2APC01HT121:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:SG2APC01HT121; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT121;
x-forefront-prvs: 0703B549E4
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(199004)(189003)(74316002)(53546011)(55016002)(87572001)(6306002)(68736007)(6436002)(54896002)(224303003)(106356001)(105586002)(82202002)(19627405001)(6606003)(76176011)(16234385003)(110136005)(7696005)(20460500001)(99286004)(33656002)(14454004)(966005)(5250100002)(25786009)(45080400002)(97736004)(104016004)(3660700001)(86362001)(6346003)(446003)(26005)(102836004)(8936002)(3280700002)(2900100001)(426003)(486006)(81156014)(476003)(11346002)(5660300001)(85182001)(48020200001); DIR:OUT; SFP:1901; SCL:1; SRVR:SG2APC01HT121; H:HK2PR02MB1251.apcprd02.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:;
received-spf: None (protection.outlook.com: outlook.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=gurong_cmcc@outlook.com;
x-microsoft-antispam-message-info: l8bLq5F5/P+La4U9iFvKHPgIOKEWwXA5SuOIEbo89PRreyOQAzS75kb42xOJ4c0qf7m1TkSF/M9vUT5Nzp+/X8Q7jwdJdaQy09HPmDqcQ1hSzSaZyetutoDdQQ1YrhxteF4BDkdWegZrErp9++qyU3l7M/13t9J4GhmGqRMiyxOld6YPJKfTDm7LSxUmJD2U
Content-Type: multipart/alternative; boundary="_000_HK2PR02MB12512D4661A80A5FE03EEB148B7D0HK2PR02MB1251apcp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-Network-Message-Id: a803aee9-89a9-46a0-c107-08d5d1b56fd8
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: c001924d-3e68-4f40-89c2-901a49278da7
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jun 2018 05:12:33.8244 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT121
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/61ezJYeq1vb5WUhxishW_Pd2Jfo>
Subject: [L2sm] =?gb2312?b?tPC4tDogIFJlo7ogUHJvcG9zZWQgTGlhaXNvbiB0byAz?= =?gb2312?b?R1BQIFNBNQ==?=
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: Thu, 14 Jun 2018 05:12:43 -0000

Hi, all.


I totally agree with the proposed liasion as 3GPP is indeed working on Management and orchestration of 5G.


Rong Gu

gurong_cmcc@outlook.com

gurong@chinamobile.com

________________________________
发件人: L2sm <l2sm-bounces@ietf.org>; 代表 Chongfeng <chongfeng.xie@foxmail.com>;
发送时间: 2018年6月9日 7:48:23
收件人: adrian; l2sm
主题: [L2sm] Re: Proposed Liaison to 3GPP SA5

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