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

Stewart Bryant <stewart.bryant@gmail.com> Tue, 01 November 2016 15:21 UTC

Return-Path: <stewart.bryant@gmail.com>
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 4CBED129A8A; Tue, 1 Nov 2016 08:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tFseI6OmOHAZ; Tue, 1 Nov 2016 08:21:49 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 EF042129A6F; Tue, 1 Nov 2016 08:21:34 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id a197so84276098wmd.0; Tue, 01 Nov 2016 08:21:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:cc:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=UAhkAXxeI4KhDXo32dkxH2NqK3LhuXzQAVxyzW6yelw=; b=Y2G/dzGXQ8lSGQlBbytXWpvpgG5Y8iIqeE2gSKDJcPnl6AEhL0dIktrjzIhJ2vIc7c 1l7/JOcZQ5yhWX/sODHqEX4ionQx052KfHjU0yHcvlOwyDcrR4MML319pJehGiI/l00p xVk+Xra+aUhaXNkiGCeUUWElJNzpYMzzissLwd2ZueF/O/kQLZAaXaOG7mO+OY/ffEiW eNpP5JmPR+HhheHEXKIEUFHAnRVn6wTch/3fWgK6SWHMhVBbQtL8A+/gqLZyZqqrNFXC IjuVIsRV8WTbrwb8QzFHZc46yFQlyPMRFrnBDQSNC9nMp4rWO2UqZ0xmZJGFWm+6JozT /qcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:cc:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=UAhkAXxeI4KhDXo32dkxH2NqK3LhuXzQAVxyzW6yelw=; b=dfpVZcHTmL/5cRQYw8++BQYqPHWFutEALjGEGPDUlN9nlb8dS6k3n5rPu+GCNXSXan 4H7vF9dOeU6jkcHaaPPrXG86apTmPzkByFeJ5kUxsLTLRYOVNDq+JxjvQt32P3XbFNEq 2HoCTnQAORqW/j8YVEkmGRP8wdW7ZSALxoudjOwmABfYVY1AD0ykNJX/766gbNUxK8eJ vtsxlxDB7FwkgrD+fv12dbHHk2OYIUg834lE5f6YsTEEO/sJ0Bo+ZSlj77QAXwQ/E1yD l2424pxOJ+l+/R9mIvE0M0mVLERXVHP5VzGRGhIOLiAoaIPYltZEP/3f2MQKqDA6buZl AthQ==
X-Gm-Message-State: ABUngvdNQmFl9feUA+6Efp4FcK1KzQ5zVrrVwsDlsppD0Nm9XfuvPVdYYNBk0+Uz9jeq8w==
X-Received: by 10.194.223.97 with SMTP id qt1mr26196123wjc.33.1478013693385; Tue, 01 Nov 2016 08:21:33 -0700 (PDT)
Received: from [192.168.2.104] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id hy10sm28462820wjb.10.2016.11.01.08.21.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Nov 2016 08:21:32 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
To: 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
Message-ID: <6761290b-eac5-8241-eb7f-32683fe594a1@gmail.com>
Date: Tue, 01 Nov 2016 15:21:30 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/7mb3k09xHP2sRIlGyfI1KzBmVTQ>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Mach Chen <mach.chen@huawei.com>
Subject: [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: Tue, 01 Nov 2016 15:21:51 -0000

(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