Re: [5gangip] 5G and Slicing

Xuxiaohu <xuxiaohu@huawei.com> Sat, 31 October 2015 08:22 UTC

Return-Path: <xuxiaohu@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 158701A1B5C for <5gangip@ietfa.amsl.com>; Sat, 31 Oct 2015 01:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 oKgA6NUYG048 for <5gangip@ietfa.amsl.com>; Sat, 31 Oct 2015 01:22:53 -0700 (PDT)
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 AE9AA1A1B34 for <5gangip@ietf.org>; Sat, 31 Oct 2015 01:22:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BZP30099; Sat, 31 Oct 2015 08:22:51 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.235.1; Sat, 31 Oct 2015 08:22:50 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.187]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0235.001; Sat, 31 Oct 2015 16:22:39 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "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/4kADyIoJQ
Date: Sat, 31 Oct 2015 08:22:39 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3F2CE@NKGEML512-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>
In-Reply-To: <05C81A773E48DD49B181B04BA21A342A33B1812D54@HE113484.emea1.cds.t-internal.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.55]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0CB3F2CENKGEML512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/5gangip/wAS5Rz9kT_AtikVmRtmB8k0Pwbs>
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: Sat, 31 Oct 2015 08:22:57 -0000


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