Re: [Stackevo-discuss] [gaia] 5G: It's the Network, Stupid

I tend to agree. A slice per user, except in exceptional cases would seem unlikely. Since a slice requires multiple resources be allocated end to end the concept most likely will work best for a set of users that share a common QOS/QOE/Admin requirement.

Essentially QOS/QOE within a slice will still have to be addressed with the tools we already have.

Peter

-----Original Message-----
From: 5gangip [mailto:5gangip-bounces@ietf.org] On Behalf Of Linda Dunbar
Sent: Thursday, December 17, 2015 12:49 PM
To: Nishanth Sastry; Jon Crowcroft
Cc: icnrg@irtf.org; gaia; stackevo-discuss@iab.org; Dirk Kutscher; marnew@iab.org; 5gangip@ietf.org; dtn-interest@irtf.org
Subject: Re: [5gangip] [Stackevo-discuss] [gaia] 5G: It's the Network, Stupid

I strongly support the concept of network slicing for Applications or IoT networks. 
But it is not realistic to expect operators networks to take control requests from individual users/handsets. There has to be an authenticated application controller that makes requests/commands to the sliced network. 

My two cents. 

Linda 

-----Original Message-----
From: Stackevo-discuss [mailto:stackevo-discuss-bounces@iab.org] On Behalf Of Nishanth Sastry
Sent: Thursday, December 17, 2015 6:43 AM
To: Jon Crowcroft
Cc: icnrg@irtf.org; gaia; stackevo-discuss@iab.org; Dirk Kutscher; marnew@iab.org; 5gangip@ietf.org; dtn-interest@irtf.org
Subject: Re: [Stackevo-discuss] [gaia] 5G: It's the Network, Stupid

E2E security in 5G can be addressed through network slicing, another concept which seems to be included in many 5G proposals. If each application has its own slice, it can screw up but wont be able to affect other applications. Within each slice, E2E security can be enforced in an application specific manner. Even better would be if we can make each flow be its own slice. This may seem to be overly heavyweight, but is along the lines of what Bromium  is trying to do for desktops, isolating processes and data from each other using
"microvisors": http://www.bromium.com/why-bromium/how-we-do-it.html We just need to do it for networks :)

nishanth
—
CD-GAIN: http://bit.ly/cd-gain
S4S: http://www.space4sharingstudy.org/
REACH: http://www.eu-india.net

5G Norma: https://5g-ppp.eu/5g-norma
VirtuWind: https://5g-ppp.eu/virtuwind/

On 17 Dec 2015, at 7:56, Jon Crowcroft wrote:

> Great article...one thing about the 4g..5g evolution is increasing 
> cooperation in forwarding and relaying signal, bits, packets (shared 
> cell tower/base station/antennae across provider). So 
> direct,mesh,adhoc stop just being edge notions, but are all first 
> class part of the architecture ("don't fear the edge"). There is huge 
> tension between this trend, and e2e security....I have not seen anyone 
> address how to resolve that tension...
> On 16 Dec 2015 6:42 pm, "Dirk Kutscher" <Dirk.Kutscher@neclab.eu>
> wrote:
>
>> [apologies for cross-posting]
>>
>>
>>
>> Hi,
>>
>>
>>
>> I have written up a few thoughts on current discussions around 5G and 
>> network evolution. I might publish this as paper later, but wanted to 
>> get it out early and ask for comments – so would be grateful for any 
>> feedback.
>> It’s not very polished and slightly long, but hopefully 
>> understandable enough. Take it as a “position paper” for now.
>>
>>
>>
>> Abstract:
>>
>> Current 5G network discussion are often focusing on providing more 
>> comprehensive and integrated orchestration and management functions 
>> in order to improve “end-to-end” managebility and programmability, 
>> derived from NGMN and similar requirements. While these are important 
>> challenges, this memo takes the perspective that in order to arrive 
>> at a more powerful network, it is important to understand the pain 
>> points and the reasons for certain design choices of today’s 
>> networks. Understanding the drivers for traffic management systems, 
>> middleboxes, CDNs and other application-layer overlays should be 
>> taken as a basis for analyzing 5G uses cases and their requirements. 
>> In this memo, I am making the point that many of today’s business 
>> needs and the ambitious 5G use cases do call for a more powerful data 
>> forwarding plane, taking ICN as an example. Features of such a 
>> forwarding plane would include better support for heterogeneous 
>> networks (access networks and whole network deployments), multi-path 
>> communication, in-network storage and implementation of operator 
>> policies. This would help to avoid overlay silos and finally simplify 
>> network management.
>>
>>
>>
>> http://dirk-kutscher.info/posts/5g-its-the-network-stupid/
>>
>>
>>
>> Thanks,
>>
>> Dirk
>>
>>
>>
>> _______________________________________________
>> gaia mailing list
>> gaia@irtf.org
>> https://www.irtf.org/mailman/listinfo/gaia
>>
>>
> _______________________________________________
> gaia mailing list
> gaia@irtf.org
> https://www.irtf.org/mailman/listinfo/gaia

_______________________________________________
Stackevo-discuss mailing list
Stackevo-discuss@iab.org
https://www.iab.org/mailman/listinfo/stackevo-discuss
_______________________________________________
5gangip mailing list
5gangip@ietf.org
https://www.ietf.org/mailman/listinfo/5gangip