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

Eliot Lear <lear@cisco.com> Mon, 16 January 2017 11:00 UTC

Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D50F1299B7 for <ietf@ietfa.amsl.com>; Mon, 16 Jan 2017 03:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level:
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 EonZecDGZt-H for <ietf@ietfa.amsl.com>; Mon, 16 Jan 2017 03:00:35 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA9BA129993 for <ietf@ietf.org>; Mon, 16 Jan 2017 03:00:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2714; q=dns/txt; s=iport; t=1484564429; x=1485774029; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=RfftHYAXyMuPgUWtWVof/xlfGSFyhTlb1LNcbqNlS2I=; b=YdaXHQXlOyDbNM3CA47q59iP2DpAktEu0vUMqJKnIVnD6KCsIcH0Pjc7 vxYQY5tKw0rjKBYKYhot6grwC0wO1hbw7cSukP2u7OvIMGM7OyAh0id+H ShVaHYh+XkK3EKumVXTqtMz11/zBafnHjlLO8mapPjtHFe/XonYmBiHon g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B3AQBTp3xY/5xdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzkBAQEBAR9fA4EGg1GKB5F2H5UsggsfC4UuSgKCID8YAQIBAQE?= =?us-ascii?q?BAQEBYyiEagEBBAEBIUsLEAsYDBsDAgInHxETBgIBAReIaA6uM4IligEBAQEBA?= =?us-ascii?q?QEEAQEBAQEUCgWIRwiCXYQaEQFogjqCXgWbOoNpgX+Ld4F3hQ6DKoY+kmwfOHE?= =?us-ascii?q?kEggVFTqEMoIBPTWGQIIuAQEB?=
X-IronPort-AV: E=Sophos;i="5.33,238,1477958400"; d="asc'?scan'208";a="372466924"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2017 11:00:28 +0000
Received: from [10.24.13.57] ([10.24.13.57]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v0GB0Qjj019523; Mon, 16 Jan 2017 11:00:27 GMT
Subject: Re: New Non-WG Mailing List: NetSlices - Network Slicing
To: ietf@ietf.org
References: <148432584523.26939.3373215722409373088.idtracker@ietfa.amsl.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <846230b9-a0c9-c62b-8897-217a4399b6a6@cisco.com>
Date: Mon, 16 Jan 2017 12:00:25 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <148432584523.26939.3373215722409373088.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fpRHiuAHa86vvJfV4L5VQl3XveOpWSj9o"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/udyspAUljTqefEnAwlAFZYknPGY>
Cc: jiangsheng@huawei.com, a.galis@ucl.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jan 2017 11:00:36 -0000

I realize that it is hard to state the definition of the term in the
announcement, especially since the point of the list is to define the
term, but perhaps the list owners could provide just a bit more context
as to what problem(s) network splicing is supposed to solve.  The
description below is a little thin on that point.

Thanks,

Eliot


On 1/13/17 5:44 PM, IETF Secretariat wrote:
> A new IETF non-working group email list has been created.
>
> List address: netslices@ietf.org 
> <mailto:netslices@ietf.org>
>
> To subscribe: https://www.ietf.org/mailman/listinfo/netslices 
> <https://www.ietf.org/mailman/listinfo/netslices>
>
> Purpose: “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."
>
> For additional information, please contact the list administrators.
>
>