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

Terry Manderson <> Tue, 17 January 2017 01:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 96AFC12996B for <>; Mon, 16 Jan 2017 17:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.4
X-Spam-Status: No, score=-7.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AZydCBmB9iQt for <>; Mon, 16 Jan 2017 17:49:25 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B30B512996D for <>; Mon, 16 Jan 2017 17:49:24 -0800 (PST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 16 Jan 2017 17:49:22 -0800
Received: from ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1178.000; Mon, 16 Jan 2017 17:49:22 -0800
From: Terry Manderson <>
To: "" <>, 'Stewart Bryant' <>, "" <>
Subject: Re: New Non-WG Mailing List: NetSlices - Network Slicing
Thread-Topic: New Non-WG Mailing List: NetSlices - Network Slicing
Thread-Index: AQHSbbM9PZ61f0YAi0CxActe+ad0vaE3MgeAgAXoHoA=
Date: Tue, 17 Jan 2017 01:49:21 +0000
Message-ID: <>
References: <> <02f401d26da8$655e7c30$301b7490$> <> <037801d26dc3$ac8edda0$05ac98e0$>
In-Reply-To: <037801d26dc3$ac8edda0$05ac98e0$>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3567498552_1257720036"
MIME-Version: 1.0
Archived-At: <>
Cc: "" <>, "" <>
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 01:49:35 -0000

Since you asked Adrian :)

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.


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?