Re: [5gangip] 5G and Slicing

"Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com> Sun, 01 November 2015 12:46 UTC

Return-Path: <walter.haeffner@vodafone.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 376041A6FC9 for <5gangip@ietfa.amsl.com>; Sun, 1 Nov 2015 04:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 7-I5JwarcC_1 for <5gangip@ietfa.amsl.com>; Sun, 1 Nov 2015 04:46:28 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) (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 A10A21A6F98 for <5gangip@ietf.org>; Sun, 1 Nov 2015 04:46:27 -0800 (PST)
Received: from [85.158.136.83] by server-13.bemta-5.messagelabs.com id EF/6B-06091-1A906365; Sun, 01 Nov 2015 12:46:25 +0000
X-Env-Sender: walter.haeffner@vodafone.com
X-Msg-Ref: server-11.tower-36.messagelabs.com!1446381984!213444!1
X-Originating-IP: [195.232.244.134]
X-StarScan-Received:
X-StarScan-Version: 7.19.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31322 invoked from network); 1 Nov 2015 12:46:24 -0000
Received: from mailout02.vodafone.com (HELO mailout02.vodafone.com) (195.232.244.134) by server-11.tower-36.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Nov 2015 12:46:24 -0000
Received: from mailint03.vodafone.com (mailint03.vodafone.com [195.232.244.200]) by mailout02.vodafone.com (Postfix) with ESMTP id 3npcZ854mZzbdMS; Sun, 1 Nov 2015 13:46:24 +0100 (CET)
Received: from mailint03.vodafone.com (localhost [127.0.0.1]) by mailint03.vodafone.com (Postfix) with ESMTP id 3npcZ845d7z16J8b; Sun, 1 Nov 2015 13:46:24 +0100 (CET)
Received: from VOEXC03W.internal.vodafone.com (voexc03w.dc-ratingen.de [145.230.101.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint03.vodafone.com (Postfix) with ESMTPS id 3npcZ83gykz16Kmy; Sun, 1 Nov 2015 13:46:24 +0100 (CET)
Received: from VOEXC25W.internal.vodafone.com (145.230.103.197) by VOEXC03W.internal.vodafone.com (145.230.101.23) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sun, 1 Nov 2015 13:46:24 +0100
Received: from VOEXM20W.internal.vodafone.com ([169.254.4.214]) by voexc25w ([145.230.103.197]) with mapi id 14.03.0224.002; Sun, 1 Nov 2015 13:46:23 +0100
From: "Haeffner, Walter, Vodafone DE" <walter.haeffner@vodafone.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>, AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>, "5gangip@ietf.org" <5gangip@ietf.org>
Thread-Topic: 5G and Slicing
Thread-Index: AdEKnYed7eXcqI1LSJ2yVaMYbwbATQAq8ucQAAZ8qZABIk/4kADyIoJQADraq8A=
Date: Sun, 01 Nov 2015 12:46:22 +0000
Message-ID: <C8C844F84E550E43865561FAE104718579DD5404@VOEXM20W.internal.vodafone.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>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3F2CE@NKGEML512-MBS.china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_C8C844F84E550E43865561FAE104718579DD5404VOEXM20Winterna_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/5gangip/dCtjHmELMj_T0SEptO9UhIWt-GM>
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: Sun, 01 Nov 2015 12:46:32 -0000

Hi Xiaohu,

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

Do you think about alternatives to 3GPP?

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

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

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; AshwoodsmithPeter; 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 - 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 - 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