Re: [Netslices] netslicing/netslices: Potential next steps

Jeff Tantsura <jefftant.ietf@gmail.com> Sun, 30 July 2017 20:51 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: netslices@ietfa.amsl.com
Delivered-To: netslices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D489312EAF0 for <netslices@ietfa.amsl.com>; Sun, 30 Jul 2017 13:51:43 -0700 (PDT)
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=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 gMXS1Ql3a21h for <netslices@ietfa.amsl.com>; Sun, 30 Jul 2017 13:51:41 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 3338312EBF7 for <NetSlices@ietf.org>; Sun, 30 Jul 2017 13:51:41 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id m85so60169382wma.0 for <NetSlices@ietf.org>; Sun, 30 Jul 2017 13:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zIkyE4ty4NTOC3Nk/vr7lWQfRP2Gu/jlMLQdRFiLKJ0=; b=fEgo5BVjoL4kYY1GC0H2To1xjSTHMC3+2ro/EBgmWXnDP0rk3IviS3NJo2AHNuM8SL EnvQYilvqIXrjeJ33QCY3ElsWmZ4h4P3AU1p8v7OZJeHGWC9C1e4PPPNZFcIs4Lnfzws pUPLYDGANvY3rBTzQHyFGIhaxuucKttEunsCnle69faZBPSoxZ4+RSXWPoiRHj0HBV47 oSjOi9q+eWzoGVwic0R5GCmrlqBz5/oo2Ces3+Dm3LTU3AHu6okkFx/KvDpzMez5CWf9 6+T5hDToqZ8kqHSjY9ftglEB9iKChTuLg5bT9D04gWjd60FiVgmmaLUXgOXUBh8JV+fv U6CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zIkyE4ty4NTOC3Nk/vr7lWQfRP2Gu/jlMLQdRFiLKJ0=; b=HE1hv1pXzzZPHms5wpkup0nP0u6duBNb3qbXMRJoU0sHLkmTH8+mZUt6Mpq2s8EToA OWw4BFu0QNSgvUqR2aexQld9qEN2nIHNhAiHA58dcyZGbquZyLIOL1tcIEwTGxjbHlj9 mktcL+o13jW05ejYAkYkwY60vaqvxTunvjdW7PT7yTD6PKHj7EnH+8KlvDn/SHBM/+Yx 18gxsPPdUDlbR4ye1KRZLoUbfpYjAvbnO6H3RXqMiqjuCTJg2ya8XUoqAK8/vZmzHuvT 6rFf/nnDSRhhSks+wqdGhC212IxcospWcIGogBP6+XmnM7SMGxNfrBDtAAjU9zTfjVdv vllQ==
X-Gm-Message-State: AIVw1126zN7zKsfOFzyVrXtnHtMhFhyZe3LjMmR2iqxGzFtWxLO7J2xM MQaJflDbBegTp6Kmi96QrC9tFDBaoA==
X-Received: by 10.80.152.227 with SMTP id j90mr7879919edb.98.1501447899654; Sun, 30 Jul 2017 13:51:39 -0700 (PDT)
MIME-Version: 1.0
References: <1a49dbe4-bd99-ef70-656b-93075775131e@cisco.com> <51e1fe1b-0eb0-3df8-ac08-bbf16059cf37@cisco.com> <4BE59E61-D0D8-4CDA-AA69-421A2FA3DEF7@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B927CE3BF21@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B927CE3BF21@NKGEML515-MBX.china.huawei.com>
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Date: Sun, 30 Jul 2017 20:51:29 +0000
Message-ID: <CAFAzdPWXX9UesP316Qyu-aj-0duFoRKapoaLa5waFd_5uFZvkw@mail.gmail.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Benoit Claise <bclaise@cisco.com>, Jari Arkko <jari.arkko@piuha.net>
Cc: IAB <iab-bounces@iab.org>, "NetSlices@ietf.org" <NetSlices@ietf.org>, "qiangli (D)" <qiangli3@huawei.com>, Yudelei <yudelei@huawei.com>
Content-Type: multipart/alternative; boundary="94eb2c1957feb52e1e05558f142a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/qb1Nx3ky15O6Ue6CJWFrLeQ5R4o>
Subject: Re: [Netslices] netslicing/netslices: Potential next steps
X-BeenThere: netslices@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is intended for discussion and review of network slicing at IETF." <netslices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netslices>, <mailto:netslices-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netslices/>
List-Post: <mailto:netslices@ietf.org>
List-Help: <mailto:netslices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netslices>, <mailto:netslices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jul 2017 20:51:44 -0000

Sheng,

Great, thanks for the update.
Would be great if you'd bring your work to IETF at a rather early stage,
otherwise there could be a rather large gap, between what we will be doing
in IETF vs your team's work. Also think about collaboration with all the
efforts you have mentioned above and how to build on top (API's, data
models) rather than trying to reinvent the wheel.
IAB/IESG will continuously direct the overall effort.

Looking forward to seeing your work.

Thanks,
Jeff
On Fri, Jul 28, 2017 at 19:00 Sheng Jiang <jiangsheng@huawei.com> wrote:

> Benoit & Jeff,
>
> Thanks for your clear advices and instructions, which we will follow. For
> me, a unified slice template/object and its management are modest work for
> IETF to start work. My team is working on such design and correspondent
> implementation. The implementation is also including orchestration
> algorithms and mapping the unified slice template/object to one/multiple
> specific network infrastructures, for which VPN, Virtual router, Detnet,
> ACTN, and other new technologies are in our consideration. We are planning
> a demonstration on this for IETF 100 Bits-N-Bites, too.
>
> Many thanks and best regards,
>
> Sheng
>
> > -----Original Message-----
> > From: Netslices [mailto:netslices-bounces@ietf.org] On Behalf Of Jeff
> Tantsura
> > Sent: Friday, July 28, 2017 1:48 AM
> > To: Benoit Claise; NetSlices@ietf.org; Jari Arkko
> > Cc: IAB
> > Subject: Re: [Netslices] netslicing/netslices: Potential next steps
> >
> > Benoit,
> >
> > Thanks for sharing.
> > As discussed – we will continue working towards narrowed down and
> realistic
> > set of requirements towards IETF, that should guide all the great work
> > happening across different area’s/wg’s.
> >
> > >From IAB that would be Jari and myself.
> >
> > Cheers,
> > Jeff (as the BoF IAB shepherd)
> >
> > -----Original Message-----
> > From: Netslices <netslices-bounces@ietf.org> on behalf of Benoit Claise
> > <bclaise@cisco.com>
> > Date: Thursday, July 27, 2017 at 10:32
> > To: <NetSlices@ietf.org>
> > Subject: [Netslices] netslicing/netslices: Potential next steps
> >
> >     Dear all,
> >
> >     Thanks for all who contributed to the netslicing BoF: the document
> >     authors, the presenters, the participants, and the chairs. During
> this
> >     week, next to BoF itself, I've had multiple opportunities to speak
> about
> >     netslicing, with some BoF proponents, with the IAB shepherds, and
> with
> >     the IESG/IAB on Friday afternoon, etc. This helped me understanding
> the
> >     different points of views and clarified some aspects.
> >
> >     It's true that the network slicing has got a specific meaning in the
> >     context of 5G, but, as Georg (as liaison) stressed: there are no 3GPP
> >     requirements for the IETF at this point in time. Nevertheless, there
> are
> >     parts that the IETF should look at. And there are parts of the
> network
> >     slicing concept that are already being worked on at the IETF. ACTN
> comes
> >     to mind, but also DETNET, and I heard of VPN+. The individual work in
> >     WGs should continue and potentially be extended.
> >
> >     Note that I carefully used the "network slicing concept" term in the
> >     previous sentence. As one important next step, it would nice to
> focus on
> >     a common "network slicing" definition, at least its meaning for the
> IETF.
> >
> >     As mentioned during the BoF, this is not the IETF role to define a
> >     complete orchestrator, controller, or NMS/OSS. This should be
> developed
> >     by an opensource project. However, what would be a practical next
> step
> >     is to specify a kind of network slicing template, with the envisioned
> >     required parameters. From there, we could determine what's missing
> > when
> >     we try to map it to a specific (IETF) technologies.
> >
> >     Let me make up an (hopefully simple) example: I would like to have a
> >     network slice with a guaranteed bandwidth b, end-to-end jitter j,
> packet
> >     loss p, end-to-end max delay d. Do we even those abilities in the
> >     underlying technologies?
> >
> >     Regards, Benoit (as the BoF responsible AD)
> >
> >
> >     _______________________________________________
> >     Netslices mailing list
> >     Netslices@ietf.org
> >     https://www.ietf.org/mailman/listinfo/netslices
> >
> >
> >
> > _______________________________________________
> > Netslices mailing list
> > Netslices@ietf.org
> > https://www.ietf.org/mailman/listinfo/netslices
>