Re: [Netslices] Preliminary charter text for discussion
Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Sun, 28 January 2018 18:22 UTC
Return-Path: <cjbc@it.uc3m.es>
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 C9B0212E873 for <netslices@ietfa.amsl.com>; Sun, 28 Jan 2018 10:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=it-uc3m-es.20150623.gappssmtp.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 A6dGkPWRm6pK for <netslices@ietfa.amsl.com>; Sun, 28 Jan 2018 10:22:10 -0800 (PST)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 8162412EB32 for <NetSlices@ietf.org>; Sun, 28 Jan 2018 10:22:09 -0800 (PST)
Received: by mail-wr0-x233.google.com with SMTP id f6so3180695wra.6 for <NetSlices@ietf.org>; Sun, 28 Jan 2018 10:22:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=it-uc3m-es.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:reply-to:to:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=lVpg3qosnwhqW4C1DS59dYUBoetTkbTiF7bMkeay3Tg=; b=SpeOhFhD+cZwvJmzgA9eurbyXmoX1alnkeuokCFIaoSPY0dhz/tw3vFuZfJsr40F0e 7aW05q+4iQ/BwgbPnevh2R4EtRQYDiptz1E7dR33igkw0meP4tV+mmcPs02qW8z1Hud+ OBaG/3jTRU7SDFx1f+UcEI52qXg7lOMIGxCf6XXt4OFkfOQu9YsDoDKZT/UFXrB80SyH PeBJQrQ56IxeQpZoWspnJmerEiPkB/AhvlsBDCNOCGVxvqA9+FHUk9uYKXpeQXCfCg47 ppG4ynOYRnS5bqFzukPhoXw5/QEz80jPta+wHPzgQ4QooiC8bMsJcLSBpShosZeaB3Q2 Qqaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :in-reply-to:references:organization:mime-version :content-transfer-encoding; bh=lVpg3qosnwhqW4C1DS59dYUBoetTkbTiF7bMkeay3Tg=; b=JwdZEOo3KUJ9ctMhtJGkqa9q9tZwqd6EMeZ/aj2HtDNbv9Y45cPm7pwFuDK5Diw4H8 y4aQNPqisKXo2PoXPbewA7z/v7V3Plfk9sKQhxjfjv7FlBsqdH8gTZN7b/vrxbFKsz3i gar21hdG4JCuFaWuwSZIzI2HKjdAh/J6nSBcRbw3TkrINPlqM8xzeWLfNWtlprtZXBdX Lp+CLqMZv3ooa1cc5vnynyps/5n54Jkr/YXzjeCehNEQNMM02apyTVd9uI40cZiMn8fd v9iDSuTR9GjIsejqqZgnarPxeYe8SGD5xu464kEVmpNmOmjFBIfaxCpkfE7AqtkeTvXv FDQQ==
X-Gm-Message-State: AKwxytdCqgmRwiFTZVTrExlu15VPsMuHt57h+XycpwPOMPhEnYLOPb0N +SfBFllnT7rS2aNpPiUtZagLYhGF
X-Google-Smtp-Source: AH8x227J6tfxS7RFuGQQgesdXhgwk+B6SZb98HENUL4XTnaTLUjiYFO6VYi1giDo7gFlpRxloRtOqQ==
X-Received: by 10.223.172.174 with SMTP id o43mr16939258wrc.121.1517163727835; Sun, 28 Jan 2018 10:22:07 -0800 (PST)
Received: from cjbc_dell.lan (2.154.161.159.dyn.user.ono.com. [2.154.161.159]) by smtp.gmail.com with ESMTPSA id r64sm7034482wma.15.2018.01.28.10.22.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 28 Jan 2018 10:22:07 -0800 (PST)
Message-ID: <1517163726.4051.23.camel@it.uc3m.es>
From: Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es>
Reply-To: cjbc@it.uc3m.es
To: Xavier de Foy <x.defoy.ietf@gmail.com>, NetSlices@ietf.org
Date: Sun, 28 Jan 2018 19:22:06 +0100
In-Reply-To: <CAHYjOTbKq5SGx2dUt5citBq=21dRYS4nK_Sebdq0nyPX9T7bLg@mail.gmail.com>
References: <CAHYjOTbKq5SGx2dUt5citBq=21dRYS4nK_Sebdq0nyPX9T7bLg@mail.gmail.com>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3-1
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/C3ScFZApFoASbE9qjcVUmvJ7qF8>
Subject: Re: [Netslices] Preliminary charter text for discussion
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, 28 Jan 2018 18:22:13 -0000
Hi Xavier, One quick comment (apologies for being inactive, and for maybe asking about something you have already discussed) from a first read: I think the Conext part should start with a 2-line definition of network slice. This should provide the context of is understood as network slice by the COMS WG. Thanks, Carlos On Sat, 2018-01-27 at 12:51 -0500, Xavier de Foy wrote: > Hi all, a group of COMS proponents prepared a preliminary charter > text, taking into account recommendations collected when discussing > the BoF request for IETF 100. > > The recommendations were for: > 1. better account of the 4 key elements used in COMS: connectivity, > compute, storage resources + network & service functions; > 2. better description of the functional blocks and their positions in > COMS; > 3. better FCAPS coverage; > 4. better coverage of the management of the data plane. > > Please share your comments on this list by Feb 1st. Other COMS > proponents are also invited to provide additional information to help > with the discussion. > > Best Regards, > Xavier, on behalf of COMS proponents. > > > I. Context > > The Common Operations and Management on Network Slices (COMS) WG > standardizes slice-level operations and management of the resources > associated with a network slice. These resources include both network > infrastructures and service functions. More specifically, network > infrastructures are normally comprised of physical/logical > connections in access, aggregation and backbone networks as well as > computing and storage elements. Meantime, service functions include > network functions and network function chains which are pre-defined > using corresponding network infrastructure elements. Such resources > may be parts of different domains enabled by different technologies. > > A "Network Slice" is realized using a collection of technologies > spanning across data, control and management planes. Many of them > rely on existing IETF technologies including both concluded and in- > progress works such as: > - Data plane: DetNet, TE-Tunnels, MPLS, Segment Routing VPNs, NVO3 > etc. > - Controller and/or control plane: ACTN, PCE and RSVP-TE (requiring > LDP, BGP, OSPF awareness at level below) etc. > - Management plane: YANG, OAM etc. > > The foundation of COMS is a technology-independent and resource- > centric management plane. In reality, the network slice provider may > have diverse technology choices in different domains due to > geographical and commercial reasons. Therefore, COMS makes no > assumption on which technology is used for specific domains. The goal > of COMS is to define a common and inter-operative management > mechanism, which is essential for the concept of network slicing > being adopted in a system with heterogeneous network infrastructures > and services functions. Major characteristics include: > - Enabling composition of slices within a single or over multiple > domains. > - Allowing the operation and management of a network slice in a > uniform manner, even when this network slice span multiple technology > and/or administrative domains. > - Enabling deployment of services over individual slices. > > II. Scope > > The WG will describe an overall architecture for network slicing. To > manage network slices in a technology-independent manner, the network > slice provider (NSP) will need to communicate with a network slice > orchestrator (NSO) over a COMS Service Delivery Interface (SDI). The > COMS SDI can also be used between network slice orchestrators, > enabling hierarchical management through the notion of network slice > subnets. Network slices will be leased to tenants, which will be able > to use Customer Service Interface (CSI) exposed by the NS provider to > run management tasks (e.g., on-demand measurement) within their slice > instance under certain policies. > > The WG will describe an information model representing a network > slice, accounting for the key elements used in network slices: > connectivity, compute, storage resources, network and service > functions — this information model includes the representation of > managed objects and corresponding management and operations, will > guide the design of data models on SDI and CSI and also will enable > orchestrators interworking. > > The WG will specify requirements, operations and management > functionalities on network slicing interfaces SDI and/or CSI > including: > 1 Network slice service profile, e.g. set by NSP over SDI, including > high-level parameters for network infrastructures and service > functions, together with their corresponding performance > requirements. > 2 Lifecycle management of network slice. > 3 Other FCAPS functions. An important task of NSP is to aggregate > faults, performance, status information and performance guarantees > for certain services. > 4 Slice composition or stitching in multi-domain environment. > 5 Slice management by the tenant under the control of NSP, including > deploying network services over a slice. > > The WG will specify requirements and functionalities of data plane > entities as needed to enable the management of network slices. For > example, this may include abstractions of policy control and > enforcement, or gateway functionalities. The WG will also study the > mapping between the abstract information model and managed entities, > and will liaise with other IETF WGs as needed. However, the WG will > not attempt to replicate data plane technologies including DetNet, > TE-Tunnels, MPLS, Segment Routing VPNs, NVO3 etc. > > III. Deliverables > > WG deliverables are listed below and may be split in any number of > documents as determined by the WG: > - Problem statement and use cases for management of network slices. > - Architecture of network slices. > - Information model(s) and operations for network slices on topics > described above in the scope section. > - SDI and CSI interface specifications and relevant YANG models. > - Study the mappings of technology independent network equipment > configurations derived from the information model towards specific > technologies and coordination with relevant WGs as needed. > > IV. Milestones > > Dec 2018 Problem Statement, use cases and architecture > Dec 2018 Common information model and related YANG model > June 2019 Network slices composition and interworking > October 2019 FCAPS management functions and operations on network > slices including abstractions of policy control and > enforcement, or gateway functionalities. > March 2020 SDI and CSI interface specifications and relevant YANG > models > > _______________________________________________ > Netslices mailing list > Netslices@ietf.org > https://www.ietf.org/mailman/listinfo/netslices
- [Netslices] Preliminary charter text for discussi… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Alex Galis
- Re: [Netslices] Preliminary charter text for disc… Carlos Jesús Bernardos Cano
- Re: [Netslices] Preliminary charter text for disc… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Pedro Martinez-Julia
- Re: [Netslices] Preliminary charter text for disc… Carlos Jesús Bernardos Cano
- Re: [Netslices] Preliminary charter text for disc… Shunsuke Homma
- Re: [Netslices] Preliminary charter text for disc… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Kiran.Makhijani
- Re: [Netslices] Preliminary charter text for disc… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Jeff Tantsura
- Re: [Netslices] Preliminary charter text for disc… qiangli (D)
- Re: [Netslices] Preliminary charter text for disc… Alex Galis
- Re: [Netslices] Preliminary charter text for disc… Jeff Tantsura
- Re: [Netslices] Preliminary charter text for disc… Liang GENG
- Re: [Netslices] Preliminary charter text for disc… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Leeyoung
- Re: [Netslices] Preliminary charter text for disc… Leeyoung
- Re: [Netslices] Preliminary charter text for disc… Liang GENG
- Re: [Netslices] Preliminary charter text for disc… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Leeyoung
- Re: [Netslices] Preliminary charter text for disc… Daniele Ceccarelli
- Re: [Netslices] Preliminary charter text for disc… Jeff Tantsura
- Re: [Netslices] Preliminary charter text for disc… Xavier de Foy
- Re: [Netslices] Preliminary charter text for disc… Kiran.Makhijani
- Re: [Netslices] Preliminary charter text for disc… Liang GENG
- Re: [Netslices] Preliminary charter text for disc… Liang GENG