RE: New Non-WG Mailing List: NetSlices - Network Slicing

"Adrian Farrel" <> Tue, 17 January 2017 03:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A0F9F129978 for <>; Mon, 16 Jan 2017 19:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lu7w9OwEUFFB for <>; Mon, 16 Jan 2017 19:11:08 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 82C571294B8 for <>; Mon, 16 Jan 2017 19:11:07 -0800 (PST)
Received: from (localhost.localdomain []) by (8.13.8/8.13.8) with ESMTP id v0H3Ag17031172; Tue, 17 Jan 2017 03:10:42 GMT
Received: from 950129200 ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id v0H3Aect031161 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 17 Jan 2017 03:10:41 GMT
From: Adrian Farrel <>
To: 'Terry Manderson' <>
References: <> <02f401d26da8$655e7c30$301b7490$> <> <037801d26dc3$ac8edda0$05ac98e0$> <>
In-Reply-To: <>
Subject: RE: New Non-WG Mailing List: NetSlices - Network Slicing
Date: Tue, 17 Jan 2017 03:10:43 -0000
Message-ID: <017c01d2706f$4b7957d0$e26c0770$>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGcZlxvgJwBaaYzBECsdPQiJ0CV9AI7lK+kAgHz8GECc9ujVQJmmGqioV9QAHA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--19.187-10.0-31-10
X-imss-scan-details: No--19.187-10.0-31-10
X-TMASE-MatchedRID: oHOSwQSJZWjDQW/tdTswLmA/V00XWjDtQKuv8uQBDjpElaZ44wdr5NJV T8Kbpe9XxONLbuQ5v4cCkGh7KtZGsHc1NHdVsdrfbMGKOuLn5FWusS9CiBzL8cWkDW4kV3WaG7a bhhh3poI5xgDdkcQloFF+gPK2wX7ElVfZ15nJ5v8a4TdTJQcbV8Z1DHUrQK2ZzED5fC5RDhoo+d 2hAeagy02OHZCohYw1wgQTtJ//HL2jbySQYqtdWtjko+KiQPUGuzfiYKZlB0Y06dhcpwNHEJwla GGOz9d3L8+ph7QK4A7MalXlQ0XZHx68k+gLxGOd8CORMyRE01SVq+okl1rYD+aE+jTWVVwjYQvz ab3G5lpNEWVDgPyDmFdTtsRgoMSj3wijxsym1h2QmLXB14cW2iQqzcugG1CVYsz9F4FLBTDcZHB 64MA3V8bQPoBDOZl3jkEQ8fIXt9O6de0YULw0FlfS8E9vfq82fS0Ip2eEHnzUHQeTVDUrItRnEQ CUU+jzjoczmuoPCq2UTGVAhB5EbQ==
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Jan 2017 03:11:10 -0000

Hello Terry,

This all seems fine and dandy, but there is a disconnect between what you say there "discussing a proposed definition" and "presenting a better formed definition to the IETF" (admirable intentions for a mailing list), and "determining an agreed IETF definition" as indicated by some of the participants on the list as well as in the revised mailing list announcement.

I hope I am not needlessly picking at words, but it seems that this disconnect could be the source of some future uncomfortable moments.

As Lou mentions, the topic seems to have avoided discussion on the TEAS list where it was invited to take place. That need not be a bad thing if the proponents need to self-organise a bit. And I see no harm in providing an archived mailing list under IETF "note well" terms for that self-organisation to take place. It's just about setting expectations of where the results of the organisation need to be taken.

(The benefits of a low bar include being able to reach your drink while in a sedentary position)

> I granted approval of this list, as a list, so that the definition of network slicing
> could be discussed in an IETF context.
> Really, it boils down to the (on list) discussion of what is a proposed network
> slicing definition that could see the IETF doing work on. So really about presenting
> a better formed definition to the IETF, for the IETF to consider at some future
> point in time. As we know with most "I have a problem that I think the IETF
> should work on" proposals we tend to ask for the problem to be defined in a way
> that does communicate the depth and breadth of the issue or the idea before a
> BOF is considered. This is where I see network slicing now. Showing that this very
> amorphous concept has the hope of some agreed shape and also that there are
> sufficient bodies to form that shape, whatever it is.
> As a mailing list (and JUSTa mailing list!) the work for the interested parties on
> that mailing list is to try to put words together that is actually meaningful in the
> IETF context. To be brutally honest I have doubts that this is possible from what I
> read to date but I do commit (as AD) to allowing discussion to occur as I'm neither
> the magistrate of taste nor the gate of interest.
> Cheers
> Terry
> On 14/01/2017, 3:37 AM, "ietf on behalf of Adrian Farrel" <
> on behalf of> wrote:
>     Thanks Stewart and Alex.
>     > This list is intended for discussion of network slicing to determine
>     > an agreed IETF definition of the term Network Slicing, problems and
>     > gaps to be covered with an aim to facilitate interoperation across
>     > different operator and vendor solutions. The list also determines (and
>     > assimilates) which elements of the slicing problems are already
>     > covered by existing IETF designs or work in progress.
>     It's good to discuss stuff.
>     How will agreement of "an IETF definition" be measured?
>     Or maybe you mean to attempt to agree a definition among the people
> subscribed to the list and propose that as a definition for use by the IETF?
>     But still, who on the list will call consensus?
>     Why is this something to be petty about?
>     Because I need to know whether this is a list I have to join and monitor in case I
> don't agree the definition, or whether that definition will come up for IETF review
> in the normal way.
>     Perhaps the AD who granted this list with this charter could speak up?
>     Adrian