Re: [DMM] FW: Network slicing side meeting at IETF97

Satoru Matsushima <satoru.matsushima@gmail.com> Tue, 15 November 2016 13:56 UTC

Return-Path: <satoru.matsushima@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF761294EC for <dmm@ietfa.amsl.com>; Tue, 15 Nov 2016 05:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 aNOG9S0rPVB2 for <dmm@ietfa.amsl.com>; Tue, 15 Nov 2016 05:56:29 -0800 (PST)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 CF1F912944E for <dmm@ietf.org>; Tue, 15 Nov 2016 05:56:28 -0800 (PST)
Received: by mail-yw0-x22a.google.com with SMTP id t125so94555647ywc.1 for <dmm@ietf.org>; Tue, 15 Nov 2016 05:56:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YsAlOrakZyPGDLrx3YfqW8L3sgM42PPTW00MWKHQl5c=; b=kyik01BXos2hqhAGJRRzeP+6kD+JEXB2FUpXQZ1vf6RwSjrSXGkMTrm0wf56o6+gI3 1BAq9m37h8/92Amo26YMzHtHO71sYyoubp6na7IVAtV2KAKI/cUP0dxdE0wIoULpkICg lngMkCo6dOTmFOv0RtLLnPskPD0bb2dHj/RaY3pD+RhlcnTWDd8kLw07gBPuZNy9nsAf TcNZbLlAYhcPIxcmNz1RCTKgMGJvAIjoAK6roOn18j7Em0XgMqOBPA3yDIWzsgw+6pia OZH8ex41g/K4MaitLavpDyzRPy2JMYTNFrYTVWEXGLL/oCDrbkC65CUvzz+e0pJ8r5M5 d5vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YsAlOrakZyPGDLrx3YfqW8L3sgM42PPTW00MWKHQl5c=; b=HVNHB9NuegclU9RtRaHrOCvpKKpo80fDmdil59whE2ldTJ2yVghGL7YMmR8Lmc8P1T S495fMlwANbZMvx055sHAwlJnAbatjDMp308KOUzFEPrzYOhz4rY97thGGZ71oDRbatf i0pTp1u2vUdnep3K0Gkn7gzjHX3uZMkuCMfbZVg8+UYMNI6eO8q4leq1ainlQJXBwZXf 0srnhAztP/pz4ZpYIYiTLFzT/J/nleH01tPA5qTjiecBvTTmXxz1At9qaTkWG0cvqnAQ 9m4yEhOtbkbxvcO4sAhS8Nai7krfS1SlA7yTnW7mdT+Pjztc0kOTCrDdzy3JD29G5iZw 6juQ==
X-Gm-Message-State: ABUngvfcayPw7v4TCNp9FNeK7+VWT5+6uXlUFovVzQwwpwtWnE4d3ReGaI9F4K8ARJIvRuhl0R5kb0X0/58+oQ==
X-Received: by 10.157.53.124 with SMTP id l57mr7842841ote.164.1479218187942; Tue, 15 Nov 2016 05:56:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.96.70 with HTTP; Tue, 15 Nov 2016 05:56:27 -0800 (PST)
In-Reply-To: <etPan.58291ec7.327b23c6.192@Kirans-iPad>
References: <etPan.58291ec7.327b23c6.192@Kirans-iPad>
From: Satoru Matsushima <satoru.matsushima@gmail.com>
Date: Tue, 15 Nov 2016 22:56:27 +0900
Message-ID: <CAFwJXX4aek5JPCO6dWmu-Jhora1f=NAjME9g36kKG5dS6ms5+w@mail.gmail.com>
To: "Kiran.Makhijani" <Kiran.Makhijani@huawei.com>
Content-Type: multipart/alternative; boundary="001a11c004e2a353d10541575275"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/ae1QGfpL6M9UcgFyOWWyv26h_Bk>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, dmm <dmm@ietf.org>
Subject: Re: [DMM] FW: Network slicing side meeting at IETF97
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2016 13:56:31 -0000

Thank you Kiran,

I had joined the slice meeting and made a comment to a DMM colleague.
# My bad I didn't know the DMM multicast draft..

Let me summarize a little bit about discussions of the slice meeting.
Many people said their thought almost about network segregation in resource
perspective,
such as bandwidth beyond L2/L3 vpns in static or dynamic way to form them.

I second anima guy that he said that slicing needs to be service aspect
rather than resource.
It looks that the service means transmission and routing aspect. In DMM
point of view,
they are underlay of mobile and FPC data-plane model will be deployed on
top of that.

The conclusion of the slice side meeting is to have a slice bof in next
IETF meeting which
would be going to invite 3GPP experts. So I think that DMM guys need to
head up.

Regards,
--satoru


On Mon, Nov 14, 2016 at 11:17 AM, Kiran.Makhijani <
Kiran.Makhijani@huawei.com> wrote:

> FYI. In case you are interested.
> -Kiran
>
>
>
> On 14 Nov 2016, at 00:51, Dongjie (Jimmy) <jie.dong@huawei.com> wrote:
>
> Dear presenters,
>
> The network slicing side meeting will be held on Tuesday 19:00-21:00 in
> Studio 3. Could you please send your presentation slides to Stewart and me
> by end of today? Thanks a lot.
>
> Best regards,
> Jie
>
> -----Original Message-----
> From: detnet [mailto:detnet-bounces@ietf.org <detnet-bounces@ietf.org>]
> On Behalf Of Dongjie (Jimmy)
> Sent: Tuesday, November 08, 2016 7:57 PM
> To: 5gangip@ietf.org; detnet@ietf.org; routing-discussion@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: Stewart Bryant; Mach Chen
> Subject: [Detnet] Network slicing side meeting at IETF97
>
> Dear all,
>
> Following on from the recent discussions on network slicing, it seems
> useful to have a side meeting during next week's IETF to see if we can
> establish a common view on the definition and scope of network slicing,
> what work is currently being undertaken in the IETF on this problem space,
> and what (if any) new IETF work would be needed to create deployable
> network solutions.
>
> To that end we propose a side meeting on the topic of network slicing and
> have got a room to have this discussion on the Tuesday evening of the
> IETF week.
>
> Meeting Name: 5G Network Slicing Side Meeting Assigned Room: Studio 3
> Assigned Date: 11/15/2016 (Tuesday) Assigned Time: 19:00 - 21:00
>
> To make the most of this time, it would be useful if a few of us introduce
> to the rest our thoughts on the subject before having an open discussion.
> We have a projector, and so those introducing an aspect of this problem can
> use slides, but slides are not required.
>
> The topics we have so far are:
>
> 1.  Network slicing problem statement  - Stewart Bryant
> https://tools.ietf.org/html/draft-dong-network-slicing-
> problem-statement-00
>
> 2.  Autonomic slicing networking  - Alex Galis
> https://tools.ietf.org/html/draft-galis-anima-autonomic-
> slice-networking-00
>
> 3.  Multicast and mobility service on demand with network slicing  -
> Truong-Xuan Do
> https://tools.ietf.org/html/draft-xuan-dmm-multicast-mobility-slicing-00
>
> If you have experiences/understanding of network slicing related use
> cases, requirements or problems etc., we welcome their inclusion in the
> agenda to help bring the rest up to speed.
>
> Following that, we propose an open discussion to establish whether there
> are work items that we need to get included in any existing IETF WG
> charter, or whether we need to initiate any new work in the IETF.
>
> If you have comments on our proposed agenda, or you want to introduce an
> aspect of the problem to the rest of the group, then please contact us with
> name of the topic and how long you need to talk about it.
>
> Many thanks and best regards,
>
> Jie/Stewart/Mach
>
>
> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com
> <stewart.bryant@gmail.com>]
> Sent: Tuesday, November 01, 2016 11:22 PM
> 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
> Cc: Mach Chen <mach.chen@huawei.com>; Dongjie (Jimmy)
> <jie.dong@huawei.com>
> Subject: Network Slicing - a suggestion that we meet to discuss in
> Seoul
>
>
>
>
> 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-stateme
> nt-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-net
> working/
>
> 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
>
>
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>
>