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

Lou Berger <lberger@labn.net> Thu, 03 November 2016 12:29 UTC

Return-Path: <lberger@labn.net>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63241129441 for <detnet@ietfa.amsl.com>; Thu, 3 Nov 2016 05:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.502
X-Spam-Level:
X-Spam-Status: No, score=-1.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 HBC4CS2vAB-R for <detnet@ietfa.amsl.com>; Thu, 3 Nov 2016 05:29:54 -0700 (PDT)
Received: from gproxy10-pub.mail.unifiedlayer.com (gproxy10-pub.mail.unifiedlayer.com [69.89.20.226]) by ietfa.amsl.com (Postfix) with SMTP id 23382129401 for <detnet@ietf.org>; Thu, 3 Nov 2016 05:29:54 -0700 (PDT)
Received: (qmail 26914 invoked by uid 0); 3 Nov 2016 12:29:51 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy10.mail.unifiedlayer.com with SMTP; 3 Nov 2016 12:29:50 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id 3QVl1u01J2SSUrH01QVojr; Thu, 03 Nov 2016 06:29:49 -0600
X-Authority-Analysis: v=2.1 cv=beT4Do/B c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=L24OOQBejmoA:10 a=48vgC7mUAAAA:8 a=Dfn5F_HDSTRTPRuEGuYA:9 a=9-ld3-btTJwvOdUT:21 a=Q3WeDe28SRiJ8yPA:21 a=pILNOxqGKmIA:10 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:Cc:References:To:Subject; bh=N/S9daUd3NyyETPIyGv/ratiZbxm74rcDqDjWcqzW1Q=; b=SWuA6YJqmUplDjC1z/r4dpWTeK dvtUkDI/DFo1XLGUs5RJ1CNHkmWvIA2tae/VJI117WXiRSv1drqcBBJSLR2Ri08Txg2KOtWQSDbHh ZlMU+DTpn4AbaB42LMwn8U+AD;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:36497 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from <lberger@labn.net>) id 1c2H9P-0002lL-6V; Thu, 03 Nov 2016 06:29:47 -0600
To: Stewart Bryant <stewart.bryant@gmail.com>, draft-dong-network-slicing-problem-statement@ietf.org
References: <6761290b-eac5-8241-eb7f-32683fe594a1@gmail.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <2baf2c39-3624-2f1a-3bec-f6936f9e9ff7@labn.net>
Date: Thu, 03 Nov 2016 08:29:46 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <6761290b-eac5-8241-eb7f-32683fe594a1@gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.85.191
X-Exim-ID: 1c2H9P-0002lL-6V
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([IPv6:::1]) [100.15.85.191]:36497
X-Source-Auth: lberger@labn.net
X-Email-Count: 13
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/lsjDB6ZWL_GUc9Q3qLoVTgYLQkM>
Cc: 5gangip@ietf.org, detnet@ietf.org, Mach Chen <mach.chen@huawei.com>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
Subject: Re: [Detnet] Network Slicing - a suggestion that we meet to discuss in Seoul
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2016 12:29:55 -0000

Circling back to the original question and based on this discussion:

>  Is there any interest in meeting up to discuss this in Seoul?

Please take a look at draft-ietf-detnet-use-cases and see if your use
case is (sufficiently covered).  If not, We can probably squeeze some
time (max 10min) to talk about the additions you'd like to see in the
use-case document as well as recap/close on any aspects of the on-list
discussion that make sense.

Just let us know and we'll see what we can do.

Lou

On 11/1/2016 11:21 AM, Stewart Bryant wrote:
> (Resent with correct draft alias)
>
> Hi,
>
> We were trying to pull together a problem statement for network slicing
> in a 5G context to understand how well the current IETF protocols 
> address this problem, what their short comings might be, and what IETF 
> work is necessary to have a deployable protocol suite to address this need.
>
> We have set down our first thoughts in
> https://tools.ietf.org/html/draft-dong-network-slicing-problem-statement-00
>
> We find that there are a number of groups doing similar work throughout 
> the IETF.
>
> The following comprehensive draft was directed at the ANIMA WG
> https://datatracker.ietf.org/doc/draft-galis-anima-autonomic-slice-networking/
>
> https://tools.ietf.org/html/draft-vonhugo-5gangip-ip-issues-00
> is a detailed discussion the position of network slicing in a contest of 
> next generation networks
>
> https://tools.ietf.org/html/draft-xuan-dmm-multicast-mobility-slicing-00
> looks at multicasting in a sliced context
>
> and
>
> https://tools.ietf.org/html/draft-ietf-teas-actn-framework-01
> looks at slicing in a context of traffic engineering.
>
> Our thoughts are that network slicing spans a number of deployment
> scenarios, and has a number of diverse applications, ranging from
> fragile applications, through to providing enhanced security and 
> availability.
>
> Elements of the problem and the resultant solution have a close affinity
> to DETNET. There is clearly an affinity with VPN technologies, although
> none of the existing VPNs provide the degree of isolation that we think
> is required.
>
> We note that there seems to be no natural home for all of the aspects
> of this problem.
>
> It therefore seems that if would be a good idea for those interested
> in this problem to get together at some point during IETF to swap notes
> and share our views on the problem space and how to move forward
> with addressing it.
>
> Is there any interest in meeting up to discuss this in Seoul?
>
> Best regards
>
> Stewart/Mach/Jie
>
>
>
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>