Re: [5gangip] 5G and Slicing

AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com> Mon, 02 November 2015 21:15 UTC

Return-Path: <Peter.AshwoodSmith@huawei.com>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1F91A1BCD for <5gangip@ietfa.amsl.com>; Mon, 2 Nov 2015 13:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.16
X-Spam-Level:
X-Spam-Status: No, score=-1.16 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_36=0.6, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 M33hUvPVA1XY for <5gangip@ietfa.amsl.com>; Mon, 2 Nov 2015 13:15:24 -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 663841A1B89 for <5gangip@ietf.org>; Mon, 2 Nov 2015 13:15:23 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CDO59073; Mon, 02 Nov 2015 21:15:19 +0000 (GMT)
Received: from SZXEML431-HUB.china.huawei.com (10.82.67.208) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 2 Nov 2015 21:15:18 +0000
Received: from szxeml559-mbs.china.huawei.com ([169.254.2.39]) by szxeml431-hub.china.huawei.com ([10.82.67.208]) with mapi id 14.03.0235.001; Tue, 3 Nov 2015 05:15:04 +0800
From: AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>, "5gangip@ietf.org" <5gangip@ietf.org>
Thread-Topic: 5G and Slicing
Thread-Index: AdEKnYed7eXcqI1LSJ2yVaMYbwbATQAq8ucQAAZ8qZABIk/4kADyIoJQADraq8AAGp+nSwApls0A
Date: Mon, 02 Nov 2015 21:15:03 +0000
Message-ID: <7AE6A4247B044C4ABE0A5B6BF427F8E20AF0BF73@szxeml559-mbs.china.huawei.com>
References: <7AE6A4247B044C4ABE0A5B6BF427F8E20AEF89B0@szxeml559-mbs.china.huawei.com> <05C81A773E48DD49B181B04BA21A342A33B17669FD@HE113484.emea1.cds.t-internal.com> <7AE6A4247B044C4ABE0A5B6BF427F8E20AEF9717@szxeml559-mbs.china.huawei.com> <05C81A773E48DD49B181B04BA21A342A33B1812D54@HE113484.emea1.cds.t-internal.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3F2CE@NKGEML512-MBS.china.huawei.com>, <C8C844F84E550E43865561FAE104718579DD5404@VOEXM20W.internal.vodafone.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB416CD@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB416CD@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.193.60.206]
Content-Type: multipart/alternative; boundary="_000_7AE6A4247B044C4ABE0A5B6BF427F8E20AF0BF73szxeml559mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.5637D268.00DC, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.39, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8e303000cb2588d1c9f7fe103df3d223
Archived-At: <http://mailarchive.ietf.org/arch/msg/5gangip/U0M-NTsnas52HwGnntMI0tmjl_U>
Subject: Re: [5gangip] 5G and Slicing
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 21:15:28 -0000

There are numerous 5G goals. If you look at the ITU-R IMT.VISION document you can see some of them.

Protocols like LISP and ICN are potentially interesting in that they address shortcomings of the current 4G core. For example ICN addresses delay issues with distant content and reduces bandwidth in the fronthaul. LISP can address the congestion at mobility gateways issues.

Anyway I think there are a couple of levels involved here. First are  the slicing mechanisms. As I mentioned various VPN technologies for L4/l2/l1 are relevant. Likewise within a slice there are enhancements for mobility, content distribution etc. that are relevant.

I think it¡¯s important to make this distinction otherwise it gets quite confusing. For example and limiting to a few examples each:

Above a Slice
- Slice control/hierarchy
- Slice data path isolation

Within a Slice
- Scaling up the mobility (i.e. distributed gateways or equivalent).
- Bandwidth optimizations, delay reductions (i.e. content distribution)
- Completely new signaling free cores for IOT etc.

Note that we are just in the process of finishing a first study on wireline gaps needed to address 5G requirements. It has quite a bit of information on ICN etc. done by members of the IRTF which could be interesting to those on this mailing list. The (very rough) document will be available next week.

Peter


From: Xuxiaohu
Sent: Sunday, November 01, 2015 8:33 PM
To: Haeffner, Walter, Vodafone DE; Dirk.von-Hugo@telekom.de; AshwoodsmithPeter; 5gangip@ietf.org
Subject: Re: 5G and Slicing


Hi Walter,



Please see my response inline.



________________________________
·¢¼þÈË: Haeffner, Walter, Vodafone DE [walter.haeffner@vodafone.com]
·¢ËÍʱ¼ä: 2015Äê11ÔÂ1ÈÕ 20:46
ÊÕ¼þÈË: Xuxiaohu; Dirk.von-Hugo@telekom.de<mailto:Dirk.von-Hugo@telekom.de>; AshwoodsmithPeter; 5gangip@ietf.org<mailto:5gangip@ietf.org>
Ö÷Ìâ: AW: 5G and Slicing
Hi Xiaohu,

Not clear to me what you have in mind. Do you think of a LISP (like) mechanism instead of GTP?

[Xiaohu] Yes. a LISP-like mechanism where xTR functionality is implemented on hosts rather than border routers. Maybe HIP is a more proper example.

Do you think about alternatives to 3GPP?

[Xiaohu] Not an alternative to 3GPP. Insteads, I think it may be worthwhile to be adopted as an optional mobility management mechanism for 3GPP especially for those low-latency communication scenarios.

Wrt ultra-low latencies a mobility use case would be autonomous cars. OK?

[Xiaohu] Car-2-Car is just one use case.

How you like to ensure ultra-fast switch-over to another cell in case of 1ms apps?

[Xiaohu] In my mind, it's better to decouple the wireless Internet access management service from the mobility managment service completely in the id/locator separation-based mobile Internet architecture. The wireless Internet access management service could be provided by any WiFi network operator and any celluar network operator. Since there is no need for them to offer wide-area mobility service anymore (i.e., they only need to allocate locators to those mobile devices on which some id/locator separation protocol is enabled), the AC or EPC functionality which allocates IP addresses (i.e., locators in this case) to mobile devices could be move to  users as close as possible. In contrast, mobility managment service could be provided by those entities who may not have any wireless network assets. To some extent, the business model of mobility managment service looks a bit similar with that of the DNS.

Best regards,
Xiaohu

There are currently ¡°cloudlets¡± on the way, that is edge clouds (at radio or BBU) supporting moving VMs which support an application moving with a user terminal. Currently becomes a part of Openstack. Driver is Satya, Carnegie Mellon University. Huawei, Vodafone are part of the project.

Fully agree with your mobility-centric Internet architecture remark.

Cheers,
Walter

Von: 5gangip [mailto:5gangip-bounces@ietf.org] Im Auftrag von Xuxiaohu
Gesendet: Samstag, 31. Oktober 2015 09:23
An: Dirk.von-Hugo@telekom.de<mailto:Dirk.von-Hugo@telekom.de>; AshwoodsmithPeter; 5gangip@ietf.org<mailto:5gangip@ietf.org>
Betreff: Re: [5gangip] 5G and Slicing



Technologies that can be used to improve IP mobility and therefore useful within a 5G slice running IPV6.

Dh> I would replace IP mobility by more general IP connectivity including: mobility, (multi-(routing)) path selection, ¡­



IMHO, a host-based id/locator separation protocol may be a very promising way to address the mobility management (MM) requirements of 5G networks, especially the ultra-low-latency requirement, since it would eliminate mobility anchors completely. Of course, it means a big Internet architecture transition. However, as two-thirds of the Internet traffic would originate with mobile devices by 2020 and smart mobility devices such as smart-phones would been more widely used by 2020, it seems reasonable for us to design a mobility-centric Internet architecture from now on.



Best regards,

Xiaohu


Cheers,

Peter

From: Dirk.von-Hugo@telekom.de<mailto:Dirk.von-Hugo@telekom.de> [mailto:Dirk.von-Hugo@telekom.de]
Sent: Tuesday, October 20, 2015 11:46 AM
To: AshwoodsmithPeter; 5gangip@ietf.org<mailto:5gangip@ietf.org>
Subject: RE: 5G and Slicing

Dear Peter,
Thanks for pointing there. I agree with most ideas, especially that slicing is one of the major new issues in 5G ¨C that may also refer to WG TEAS (Traffic Engineering Architecture and Signaling) and the concepts discussed there, especially with respect to drafts on ACTN (Abstraction and Control of TE Networks).
With respect to your 4th comment on ¡®non-ip ICN¡¯ (here: Information-Centric Networking?) my question would be:
- Do you mean non-IETF since ICNRG is an IRTF group (with drafts on IP isssues such as https://tools.ietf.org/html/draft-irtf-icnrg-challenges-02)?
- Or do you rather suggest to discuss also below-L3 naming issues for multi-path or heterogeneous RAN control?
My feeling is that the latter item would be slightly out of scope in an IP-related discussion, let alone that cross layer information from L2 could assist L3 decisions in finding best IP addresses for routing paths etc. ¡­
Or did I misunderstand you?
Thanks and Best Regards
Dirk

From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of AshwoodsmithPeter
Sent: Montag, 19. Oktober 2015 20:40
To: 5gangip@ietf.org<mailto:5gangip@ietf.org>
Subject: [5gangip] 5G and Slicing

Greetings, just noticed the creation of this mailing list, not sure how much discussion has already occurred but thought I would mention a couple of points briefly.

1 ¨C the concept of network slicing for 5G (the end to end ability to create multiple logical 5G networks from a physical infrastructure) most likely is relevant to all the different VPN technologies standardized at the IETF.

2- This could include GMPLS/WSON related TDM/DWDM to chop up the optical/TDM layer, IP VPN¡¯s and all their flavors including VxLan etc. to slice at the packet layer and SDN/NFV for slicing of resources in the DC.

3-V6 and mobility within a slice for packet core behaviors.

4-new ¡®non ip¡¯ protocols like ICN within a slice for new applications with different RAT¡¯s.

Cheers,

Peter