Re: [Nfvrg] [Detnet] [5gangip] Network Slicing - a suggestion that we meet to discuss in Seoul

Joe Touch <touch@isi.edu> Wed, 02 November 2016 14:06 UTC

Return-Path: <touch@isi.edu>
X-Original-To: nfvrg@ietfa.amsl.com
Delivered-To: nfvrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1322129661; Wed, 2 Nov 2016 07:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=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 reziwH2BFrjH; Wed, 2 Nov 2016 07:06:00 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 ACC1C12964C; Wed, 2 Nov 2016 07:06:00 -0700 (PDT)
Received: from [192.168.1.158] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id uA2E5S27017755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 2 Nov 2016 07:05:30 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@isi.edu>
X-Mailer: iPad Mail (14B72)
In-Reply-To: <0aaf6a442c9941d4baf9b3f0a0003182@XCH-RCD-001.cisco.com>
Date: Wed, 02 Nov 2016 07:05:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5210F394-5D68-44C6-8A78-12F80EE19B19@isi.edu>
References: <6761290b-eac5-8241-eb7f-32683fe594a1@gmail.com> <344f12df-4f25-c7ce-ec38-1354f7fca90e@isi.edu> <251f8c92-45f5-00ac-4507-173404df7329@gmail.com> <96fd1dc8-31ea-887b-3ea1-d742758935cd@isi.edu> <0aaf6a442c9941d4baf9b3f0a0003182@XCH-RCD-001.cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
X-MailScanner-ID: uA2E5S27017755
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfvrg/a3z3NuSoxcPInLpEzNFcSKy2GQk>
X-Mailman-Approved-At: Wed, 02 Nov 2016 08:02:49 -0700
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Mach Chen <mach.chen@huawei.com>, "draft-ietf-teas-actn-framework@ietf.org" <draft-ietf-teas-actn-framework@ietf.org>, "draft-galis-anima-autonomic-slice-networking@ietf.org" <draft-galis-anima-autonomic-slice-networking@ietf.org>, "nfvrg@irtf.org" <nfvrg@irtf.org>, "5gangip@ietf.org" <5gangip@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>, "detnet@ietf.org" <detnet@ietf.org>, "draft-vonhugo-5gangip-ip-issues@ietf.org" <draft-vonhugo-5gangip-ip-issues@ietf.org>, "draft-xuan-dmm-multicast-mobility-slicing@ietf.org" <draft-xuan-dmm-multicast-mobility-slicing@ietf.org>
Subject: Re: [Nfvrg] [Detnet] [5gangip] Network Slicing - a suggestion that we meet to discuss in Seoul
X-BeenThere: nfvrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Network Function Virtualization Research Group \(NFVRG\) discussion list" <nfvrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nfvrg>, <mailto:nfvrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfvrg/>
List-Post: <mailto:nfvrg@irtf.org>
List-Help: <mailto:nfvrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nfvrg>, <mailto:nfvrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2016 14:06:06 -0000


> On Nov 2, 2016, at 3:40 AM, Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
> 
> Looks correct, Joe, but then overlays as we traditionally see them do not necessarily provide the degree of isolation that we seem to be after here.

It seems like you're just noting that most Internet overlays don't bother with provisioning...

> 
> And this is where DetNet comes into play. At the extreme of the definition, a deterministic flow will traverse the network is such a fashion that the influence from other flows is not observable on that flow, e.g., no jitter and no congestion loss induced by other flows holding or clogging a link somewhere down in the fabric. Which means that one overlay will experience the same connectivity as if the nodes that compose it were physically meshed with serial wires. 

If you're talking about a flow on an otherwise empty overlay, that is just a fully provisioned overlay. If you're talking about multiple flows within an overlay being isolated this way, it's not and Internet overlay. Maybe an ATM overlay.

But these are still IMO examples of provisioning - the kind we have been dong since the phone network for over 50 years. No need for new marketing terms.

Joe

> 
> Cheers,
> 
> Pascal
> 
> -----Original Message-----
> From: detnet [mailto:detnet-bounces@ietf.org] On Behalf Of Joe Touch
> Sent: mardi 1 novembre 2016 23:35
> To: Stewart Bryant <stewart.bryant@gmail.com>; 5gangip@ietf.org; detnet@ietf.org; nfvrg@irtf.org; draft-galis-anima-autonomic-slice-networking@ietf.org; draft-vonhugo-5gangip-ip-issues@ietf.org; draft-xuan-dmm-multicast-mobility-slicing@ietf.org; draft-ietf-teas-actn-framework@ietf.org
> Cc: Dongjie (Jimmy) <jie.dong@huawei.com>; Mach Chen <mach.chen@huawei.com>
> Subject: Re: [Detnet] [5gangip] Network Slicing - a suggestion that we meet to discuss in Seoul
> 
> 
> 
>> On 11/1/2016 12:39 PM, Stewart Bryant wrote:
>> Joe, we possibly have different ideas as to what network slicing is.
>> 
>> My assumption is that it is a way that we can create multiple 
>> virtually networks over a common base network with a higher degree of 
>> isolation between VPNs and much higher performance guarantees than we 
>> currently achieve.
>> 
>> If we need a new name, we need a new name, but the concept does not 
>> seem to align with the definition you hints at.
> 
> Right. That's because you're describing an overlay.
> 
> Overlays have varying degrees of isolation and performance (and isolation and performance assurance), and always have.
> 
> There's no new term needed for that.
> 
> Joe
> 
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet