Network slicing side meeting at IETF97

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 08 November 2016 10:57 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B5B129BB9; Tue, 8 Nov 2016 02:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.718
X-Spam-Level:
X-Spam-Status: No, score=-5.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] 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 5FlSKcb0wov6; Tue, 8 Nov 2016 02:57:13 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE8E312999C; Tue, 8 Nov 2016 02:57:00 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CUT32262; Tue, 08 Nov 2016 10:56:58 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 8 Nov 2016 10:56:56 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Tue, 8 Nov 2016 18:56:44 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "5gangip@ietf.org" <5gangip@ietf.org>, "detnet@ietf.org" <detnet@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>, "nfvrg@irtf.org" <nfvrg@irtf.org>, "draft-galis-anima-autonomic-slice-networking@ietf.org" <draft-galis-anima-autonomic-slice-networking@ietf.org>, "draft-vonhugo-5gangip-ip-issues@ietf.org" <draft-vonhugo-5gangip-ip-issues@ietf.org>, "draft-xuan-dmm-multicast-mobility-slicing@ietf.org" <draft-xuan-dmm-multicast-mobility-slicing@ietf.org>, "draft-ietf-teas-actn-framework@ietf.org" <draft-ietf-teas-actn-framework@ietf.org>
Subject: Network slicing side meeting at IETF97
Thread-Topic: Network slicing side meeting at IETF97
Thread-Index: AdI5rrdXHNib4ji2TnCjLB5Ihir3sg==
Date: Tue, 8 Nov 2016 10:56:43 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C92793509382@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.151.75]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.5821AF7B.0002, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a133b9d8038f39465106332379cf2f0d
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/jadRTYHtWjfICRRzWMiXLLsJlio>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2016 10:57:22 -0000

Dear all,

Following on from the recent discussions on network slicing, it seems useful to have a side meeting during next week's IETF to see if we can establish a common view on the definition and scope of network slicing, what work is currently being undertaken in the IETF on this problem space, and what (if any) new IETF work would be needed to create deployable network solutions.

To that end we propose a side meeting on the topic of network slicing and have got a room to have this discussion on the Tuesday evening of the IETF week.
 
Meeting Name: 5G Network Slicing Side Meeting 
Assigned Room: Studio 3 
Assigned Date: 11/15/2016 (Tuesday)
Assigned Time: 19:00 - 21:00

To make the most of this time, it would be useful if a few of us introduce to the rest our thoughts on the subject before having an open discussion. We have a projector, and so those introducing an aspect of this problem can use slides, but slides are not required.

The topics we have so far are:
  
1.  Network slicing problem statement  - Stewart Bryant
https://tools.ietf.org/html/draft-dong-network-slicing-problem-statement-00

2.  Autonomic slicing networking  - Alex Galis
https://tools.ietf.org/html/draft-galis-anima-autonomic-slice-networking-00

3.  Multicast and mobility service on demand with network slicing  - Truong-Xuan Do
https://tools.ietf.org/html/draft-xuan-dmm-multicast-mobility-slicing-00

If you have experiences/understanding of network slicing related use cases, requirements or problems etc., we welcome their inclusion in the agenda to help bring the rest up to speed.

Following that, we propose an open discussion to establish whether there are work items that we need to get included in any existing IETF WG charter, or whether we need to initiate any new work in the IETF.

If you have comments on our proposed agenda, or you want to introduce an aspect of the problem to the rest of the group, then please contact us with name of the topic and how long you need to talk about it.

Many thanks and best regards,

Jie/Stewart/Mach


> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, November 01, 2016 11:22 PM
> To: 5gangip@ietf.org; detnet@ietf.org; nfvrg@irtf.org;
> draft-galis-anima-autonomic-slice-networking@ietf.org;
> draft-vonhugo-5gangip-ip-issues@ietf.org;
> draft-xuan-dmm-multicast-mobility-slicing@ietf.org;
> draft-ietf-teas-actn-framework@ietf.org
> Cc: Mach Chen <mach.chen@huawei.com>om>; Dongjie (Jimmy)
> <jie.dong@huawei.com>
> Subject: Network Slicing - a suggestion that we meet to discuss in Seoul
> 
> 
> 
> 
> Hi,
> 
> We were trying to pull together a problem statement for network slicing in a 5G
> context to understand how well the current IETF protocols address this
> problem, what their short comings might be, and what IETF work is necessary
> to have a deployable protocol suite to address this need.
> 
> We have set down our first thoughts in
> https://tools.ietf.org/html/draft-dong-network-slicing-problem-statement-00
> 
> We find that there are a number of groups doing similar work throughout the
> IETF.
> 
> The following comprehensive draft was directed at the ANIMA WG
> https://datatracker.ietf.org/doc/draft-galis-anima-autonomic-slice-networking/
> 
> https://tools.ietf.org/html/draft-vonhugo-5gangip-ip-issues-00
> is a detailed discussion the position of network slicing in a contest of next
> generation networks
> 
> https://tools.ietf.org/html/draft-xuan-dmm-multicast-mobility-slicing-00
> looks at multicasting in a sliced context
> 
> and
> 
> https://tools.ietf.org/html/draft-ietf-teas-actn-framework-01
> looks at slicing in a context of traffic engineering.
> 
> Our thoughts are that network slicing spans a number of deployment scenarios,
> and has a number of diverse applications, ranging from fragile applications,
> through to providing enhanced security and availability.
> 
> Elements of the problem and the resultant solution have a close affinity to
> DETNET. There is clearly an affinity with VPN technologies, although none of
> the existing VPNs provide the degree of isolation that we think is required.
> 
> We note that there seems to be no natural home for all of the aspects of this
> problem.
> 
> It therefore seems that if would be a good idea for those interested in this
> problem to get together at some point during IETF to swap notes and share our
> views on the problem space and how to move forward with addressing it.
> 
> Is there any interest in meeting up to discuss this in Seoul?
> 
> Best regards
> 
> Stewart/Mach/Jie
> 
> 
>