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

Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> Wed, 23 December 2015 09:09 UTC

Return-Path: <crowcroft@gmail.com>
X-Original-To: stackevo-discuss@ietfa.amsl.com
Delivered-To: stackevo-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 331AD1A874C; Wed, 23 Dec 2015 01:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 dANVvd4gUTuB; Wed, 23 Dec 2015 01:09:50 -0800 (PST)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EC3A1ACDFA; Wed, 23 Dec 2015 01:09:48 -0800 (PST)
Received: by mail-lf0-x234.google.com with SMTP id l133so142739761lfd.2; Wed, 23 Dec 2015 01:09:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=sP3o1WqV7FQQBFWHXbOlP8Ab9ZYoub0rWALvOUKMGIA=; b=qvvY83tM9a7tkWHqXmEafFO1IKdeWIzkAQ+wU1GwktcdBdDCZ5j0FxUELt/MkKfcpQ 7FDaRGvo8YwumS3mem19QmKxu4ewWYPk5LaDX3zlnd3xvMspYKAKtmKaq9JvB1GkJkQK CvyDTbXDTIQgy9WTAN5FhstbxT9JT6SOtgNeU+XJSGPtZ4ha+q0FjfZbZaELXlVRootZ P/pUJGM8EV/+LB6SH4LTFCAxamf4RqyR57EwqtF+hRXOsXmeHiT7FqF6ZqCir4FdGSnk T1N0VJucXN20tAMvcRuMjpiFy3IYtrFh2+2P98AmDFIo/0DSqwIrispjuzWWUBQb5p8Y 3w+Q==
MIME-Version: 1.0
X-Received: by 10.25.86.9 with SMTP id k9mr10367527lfb.36.1450861786135; Wed, 23 Dec 2015 01:09:46 -0800 (PST)
Sender: crowcroft@gmail.com
Received: by 10.25.21.200 with HTTP; Wed, 23 Dec 2015 01:09:45 -0800 (PST)
In-Reply-To: <7AE6A4247B044C4ABE0A5B6BF427F8E20AF3BC87@szxeml559-mbs.china.huawei.com>
References: <82AB329A76E2484D934BBCA77E9F5249A682F744@Hydra.office.hd> <CAEeTej+pHehyX7+qteogQcAkCcJKYhZoQKStuXGmAzWRj1_rXQ@mail.gmail.com> <F8355406-91C7-4B96-995C-1AD9D7997DC1@kcl.ac.uk> <4A95BA014132FF49AE685FAB4B9F17F657DB3A7F@dfweml701-chm> <56789156.2020704@isi.edu> <6EE22057-5EB9-4489-A50D-7B92DA2B96AF@gmail.com> <5679857D.9000602@isi.edu> <7AE6A4247B044C4ABE0A5B6BF427F8E20AF3BC87@szxeml559-mbs.china.huawei.com>
Date: Wed, 23 Dec 2015 09:09:45 +0000
X-Google-Sender-Auth: -0za28PDJvinzAjjORt8s7_Yrcw
Message-ID: <CAEeTejLbi8WVbuTfdSQVZETzjiK8nM57175QfT5dE8QB5FSjTA@mail.gmail.com>
From: Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk>
To: AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>
Content-Type: multipart/alternative; boundary=001a1141245c61858a05278d156a
Archived-At: <http://mailarchive.ietf.org/arch/msg/stackevo-discuss/VXzcsFQdpGf3pgDMMurpzpsNk7Q>
X-Mailman-Approved-At: Wed, 30 Dec 2015 05:00:45 -0800
Cc: "icnrg@irtf.org" <icnrg@irtf.org>, Joe Touch <touch@isi.edu>, gaia <gaia@irtf.org>, "stackevo-discuss@iab.org" <stackevo-discuss@iab.org>, Linda Dunbar <linda.dunbar@huawei.com>, "marnew@iab.org" <marnew@iab.org>, Dino Farinacci <farinacci@gmail.com>, "5gangip@ietf.org" <5gangip@ietf.org>, Nishanth Sastry <nishanth.sastry@kcl.ac.uk>, Dirk Kutscher <Dirk.Kutscher@neclab.eu>, "dtn-interest@irtf.org" <dtn-interest@irtf.org>
Subject: Re: [Stackevo-discuss] [5gangip] [gaia] 5G: It's the Network, Stupid
X-BeenThere: stackevo-discuss@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP Stack Evolution Discussion List <stackevo-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stackevo-discuss/>
List-Post: <mailto:stackevo-discuss@iab.org>
List-Help: <mailto:stackevo-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Dec 2015 09:09:52 -0000

very well said

vpns are one (or 2) dimensions of a slice - but slices are cross layer
resource pooling with isolation -
many new(er) wireless nets need to share resources at antennae and
symbol/code and forwarding/relaying levels to maximise capacity, and _then_
isolate pools of resource for given users for QoE/QoS etc reasons - you
might subsume the name VPN, but I think that'd be over-reach..

actually designing a cooperative mimo system also has the interesting
effect of making you revisit e2e security properly too

(at the routing level, sharing resources kind of wreaks havoc with current
BGP design/ practice too I believe:)

if we assume the future smart city might have about the same number of
internet end systems as the whole internet does today, and more providers
(every home&autonomous-car/bike is a provider), there's a lot to challenge
current architects, and get done before christmas

On Tue, Dec 22, 2015 at 6:47 PM, AshwoodsmithPeter <
Peter.AshwoodSmith@huawei.com> wrote:

> Couple of comments from my perspective before disappearing for Xmas.
>
>
>
> > Slices have the baggage that a process can belong to only one slice at a
> time.
>
>
>
> Not always. A process which is implementing an air interface could in fact
> be implementing several slices in the same process. Or same core.
>
>
>
> > Why does yet another term need to be defined for what has been
> traditionally called a multi-tenant VPN.
>
>
>
> I believe a slice is much more than a VPN however VPN technologies are
> likely a component part of what a slice 'is'.
>
>
>
> Here is a definition I have found helpful:
>
>
>
> To define a slice we need to look at it from the perspective of both the
> end devices (1) and the network (2) so:
>
>
>
> (1)   From the perspective of the end devices it’s relatively simple. A
> slice is a way to group end devices that share common QOS/QOE and
> Administration/Geographic area etc.
>
>
>
> (2)   From the perspective of the network a slice is much more
> complicated. Essentially a slice is a set of subsets of the all the network
> equipment that makes up the 5G network from Antennas through to core
> processing. Thus
>
> Slice_i =   Subset of(All_Antennas)        U
>
>             subset of(All_Fronthaul)       U
>
>             Subset of(All CRAN fabric)     U
>
>             Subset of(All CRAN processing) U
>
>             Subset of(ALL Numerologies)    U
>
>             Subset of(All DC fabric)       U
>
>             Subset of(All DC processing)
>
>
>
> Where of course Subset(X) can contain all or none of the elements in X.
>
>
>
> So to bring up a slice we need to allocate antennas, configure the
> fronthaul to the CRAN fabric, allocate the CRAN fabric, allocate processing
> resources ( shared or unique in the CRAN), populate those processing
> resources with the code (Numerology) that implements the RAT, then we need
> to allocate packet backhaul bandwidth in the CRAN or DC fabric, then assign
> compute resources (shared or stand alone for the packet core processing).
>
>
>
> From this we can see that a multi tenant VPN can be used to implement a
> subset of a DC fabric and interconnect a subset of all DC processing.
> However there are a number of other areas of interest to the implementation
> of a slice that are well outside the scope of a VPN.
>
>
>
> Note also that a slice can be isolated from another slice in time, space,
> frequency or statistically in each of those subsets and in particular the
> fronthaul and RAT require very hard boundaries between slices while as we
> get further towards packet processing the boundaries can be less ridgid.
>
>
>
> Hence the need for a new term.
>
>
>
> Peter
>
>
>
>
>
>
>