[Teas] Network Slicing Design Team

Vishnu Pavan Beeram <vishnupavan@gmail.com> Wed, 18 September 2019 16:40 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D821200D8; Wed, 18 Sep 2019 09:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 PVxL1YR0-18C; Wed, 18 Sep 2019 09:40:31 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 516A6120045; Wed, 18 Sep 2019 09:40:31 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id b128so358039pfa.1; Wed, 18 Sep 2019 09:40:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=GUmN6QZbeUAxA4RhL9ZrY3bokgNHMqo2+5mrEatkYlQ=; b=GzfH7AMDuthDPY+vF4mW63qdPgarEloqmEDwlfcuawHt7ZQIm/ylo+oNOFDzIHSoYG 7ONVlFlWtfqgyvdqOj1kZzst6PnrU7bp8ypmI2gzD0UcAyu0a7aDPAjZt2/5h/SW4ZS6 bWWgyIKxBTrCjauTBRKeL1aWj9I2k8f3unHVRnS6/UIWCSAu75mwAurhL0jgo8xl7afE RR2Nf6q4/ZfjbHDJFvO587uafwiqYBq8RI31cDpe7hIwfIbHEZlR++5sIHkWRaDbq1NK EhPD55ICGPsYZ3t3Zo85G5Oc21jKokJgPI4W5oU97fiNDSIYVf+cl3fb3SnpHlCXoKMf eqlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=GUmN6QZbeUAxA4RhL9ZrY3bokgNHMqo2+5mrEatkYlQ=; b=UAOSbA3P3BuZK/ljbzMVOB0aEOhRDh8kefclnbUmqOGT4qMtZeccrK/Who0/DkAL+y YvD1cgthNS2j9prUsHfr39dwAhbj/6Zv125fklnHA/bpRPFQqUzGgFEFRV7cpxfdmT1m 7S8uCa7IBEw4blgoJT/eYHH2/HpHIOel6xep3I1pzOVjx4xcuMw7bXdonTBCJVWIahSN hn8fws8ruse5qMGxXWX+r5kyZ3GiiFDdeSi29XyQ9zF3jr3qX4hiSPR2/GxeAoGSosxi ju171JZsfyDPt3nQCXdNGPVcg32+vWQWclgbPySwCkAhcCGqwTN1vOtZQNAL3mtJJxMp x8fg==
X-Gm-Message-State: APjAAAXzflEK/JpeMnmzpFkjO1vcjs5bW30nx9c+og3J72XqjWzvVf19 PUfeun0ytdSFyN+w/9VAl/NSp9hO/66wbg6YDEQn1NfnDa8=
X-Google-Smtp-Source: APXvYqx5f/1cS1TD8kH0oRpBBCQVeoa29USbxf/PVGHDroXuLljvezQH4HKHRf35Yjb5clAggdGxvNW/PRuX4hKORFI=
X-Received: by 2002:aa7:9a48:: with SMTP id x8mr5008297pfj.201.1568824830503; Wed, 18 Sep 2019 09:40:30 -0700 (PDT)
MIME-Version: 1.0
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Wed, 18 Sep 2019 11:40:18 -0500
Message-ID: <CA+YzgTvPnMB9V9VWWeTtd4614SkgCksEa_k1JfLq-NVUPKQPPw@mail.gmail.com>
To: TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bcaf2f0592d67e40"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/jiHWXU_i5kK5BzjRffFbYnbZJfs>
Subject: [Teas] Network Slicing Design Team
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 16:40:36 -0000

WG,
    This message announces the formation of the TEAS Network Slicing Design
Team.  The objectives and deliverables for the design team have been
updated based on public and private feedback and is enclosed. There are
changes from what was previously announced in (
https://mailarchive.ietf.org/arch/msg/teas/H3azyFI3kIaZDhxwEcSK1_O2CRA),
notably calling out scope as being focused on TE technology as the basis
for the DT’s work.

We thank all who expressed interest and willingness to join the design
team.  As we’re sure all will understand, it was not possible to include
all who volunteered in the team.  The aim of the DT remains to produce
documents that will follow the normal working process, so all will be able
to participate in and contribute to this work once we have a WG document as
it progresses through normal WG processing.  We do note that the objective
of the DT is to produce an initial draft and there is no requirement for
document authorship to be limited to or include all DT members, and as
usual, we expect a WG document to reflect actual contribution to the work.

Thank you,
WG Chairs: Pavan, Lou
DT Lead: Jari Arkko

TEAS Network Slicing Design Team (Draft)

The topic of “Slicing” has received significant industry attention due to
its  role in 5G networks.  General background on slicing can be found in
[1], but it is a broad topic that covers many different aspects from
business roles to services and networks.

Within the IETF the discussion has largely focused on the narrower topics
of “Network Slicing” and “Service Chaining”. [2] provides a sample list of
related individual contributions. Much of the IETF discussion has focused
on how the combination of VPN and TE technologies can be used to deliver
Network Slices. The TEAS Network Slicing Design Team (NSDT) is being formed
to develop a framework for providing Network Slicing using IETF TE
technologies. The expectation is for IETF technologies such as IP, MPLS and
GMPLS, to  be used to create specific, isolated, and managed network
instances. The use of such technology in networks and other SDOs is up to
others; this work does not imply that the IETF specifies how slicing in any
particular setting should be done.

The primary goal of the design team is to determine how existing
technologies can be used, but it is possible that some extensions to those
technologies are needed. If such extensions relate to technology from
another working group, any eventual work belongs to that group. The reuse
of definitions and technologies developed by other SDOs is also in scope,
although extensions to such will be done in the appropriate SDO. An
important early deliverable to the working group from the design team will
be a proposed refinement of what is in-scope and what is out-of-scope for
the WG on this topic.

The design team will have the flexibility to decide on how best to develop,
document and present its work. The design team will provide regular updates
and reports to the TEAS working group.  It will present an update on their
status and plans at IETF 106 (Singapore) - which will hopefully include an
initial discussion on scope.  For  IETF 107 (Vancouver) the goal for the
design team is an initial design team framework, and possibly draft, in
time for discussion at the meeting.  A stable draft is targeted for
discussion at IETF 108. Note authorship of design team draft(s) will be
based on contribution to the work, not membership in the design team. Once
the draft is accepted as a working group document, it will progress per
TEAS working group normal process.

The design team mailing list has been set up with the membership of this
list limited to the design team and the chairs, but its archive is open and
any may send to this list.  Design team meetings will be announced on the
list and open to all.  The specific workings, including meeting schedules,
of the design team are the discretion of the team.

The mailing list for the design team is: teas-ns-dt@ietf.org
The archive can be found at:
https://mailarchive.ietf.org/arch/browse/teas-ns-dt/

The members of the design team are:
    Aijun Wang <wangaijun@tsinghua.org.cn>;
    Belo, Sergio <sergio.belo@nokia.com>;
    Dong Jie (Jimmy)  <jie.dong@huawei.com>;
    Eric Gray <eric.gray@ericsson.com>;
    Geng Xuesong <gengxuesong@huawei.com>;
    Jari Arkko <jari.arkko@ericsson.com>;                 [Lead]
    Jeff Tantsura <jeant.ie@gmail.com>;
    John E Drake <jdrake@juniper.net>;
    Luis M. Contreras <contreras.ie@gmail.com>;
    Rakesh Gandhi  <rgandhi@cisco.com>;
    Ran Chen <chen.ran@zte.com.cn>;
    Ricard Vilalta <ricard.vilalta@cc.es>;
    Rokui, Reza <reza.rokui@nokia.com>;
    Ron Bonica <rbonica@juniper.net>;
    Tomonobu Niwa <to-niwa@kddi.com>;
    Xufeng Liu <xufeng.liu.ie@gmail.com>;



[1] Background documents defining slicing in general:
https://5g-ppp.eu/wp-content/uploads/2019/07/5G-PPP-5G-Architecture-White-Paper_v3.0_PublsicConsultation.pdf
and https://www.3gpp.org/ftp/Specs/archive/28_series/28.530/28530-f10.zip
[2] IETF drafts related to the general topic of network slicing:
draft-ali-spring-network-slicing-building-blocks
draft-arkko-arch-virtualization
draft-bryant-rtgwg-enhanced-vpn
draft-defoy-netslices-3gpp-network-slicing
draft-dong-lsr-sr-enhanced-vpn
draft-dong-network-slicing-problem-statement
draft-dong-rtgwg-enhanced-vpn-protocol
draft-dong-spring-sr-for-enhanced-vpn
draft-dong-teas-enhanced-vpn
draft-drake-bess-enhanced-vpn
draft-eastlake-bess-enhance-evpn-all-active
draft-flinck-slicing-management
draft-galis-netslices-revised-problem-statement
draft-ietf-teas-enhanced-vpn
draft-king-teas-applicability-actn-slicing
draft-lee-rtgwg-actn-applicability-enhanced-vpn
draft-netslices-usecases
draft-peng-lsr-network-slicing
draft-rokui-5g-transport-slice
draft-qiang-coms-netslicing-information-model
draft-xuan-dmm-multicast-mobility-slicing
draft-zch-lsr-isis-network-slicing
draft-zhuang-bess-enhanced-vpn-auto-discovery