[Teas] Network Slicing Design Team - Draft Charter

Vishnu Pavan Beeram <vishnupavan@gmail.com> Tue, 03 September 2019 22:35 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0B0E712004F; Tue, 3 Sep 2019 15:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id kKHYrlicAqZh; Tue, 3 Sep 2019 15:35:46 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 2687D12082C; Tue, 3 Sep 2019 15:35:46 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id y22so6173255pfr.3; Tue, 03 Sep 2019 15:35:46 -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=gqUYx+exwqgUOGIZhEu3YvAmgxyRSXSUScnu4HCZKYA=; b=infDUw56U3ef1+FHYOeLg4Wnl25d4IYUSH4XK8W6BrevcZkdPy+ctmRh3p4pVmsCAa G89R7DgBbGKwCNrycZ7LAmEQEs3s0JHRtXA2ugcXoL/wi20jVCWcRjKoQU4ZVQlc+ZeK qWRdgaJHJ/ONkGrgiVvfe65atTyGF6RA4zc0deVJuUYZlJeNpb5HGzBPBn47AmDqZN7u vqtiYKeITNMi/H7EPvMo8LNjyOa2b6o7we7jjLNaVuIYTUCnalJzjwF4rAtjx6mCTCsd dk3YjbFcOU8lboheyu7fkVsyV0wdkFdOBsP0hGdrkDkBNBdUcnpHVtQLa5dWp1dfGO1k cNwQ==
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=gqUYx+exwqgUOGIZhEu3YvAmgxyRSXSUScnu4HCZKYA=; b=pp+FIM01m62sxE00JzETTnK+GBpkDFo4jkp3UWy3gz3jGnGuIb/zfFYbuQ4MRgGnbM G9hv0+mzJgX7k0DsBy0Tlr+hXIoUaoYTRbi9B+pZQCViobmKI0yrpIq7Q6Kdd1hMbTZ1 Oz7HeH7YPCiIzNUisxByYV0vFyE8eMG2jP7/6GzMi2YcyxdEpblLAQ2jYUJe/y0LGhaY ZCLwvbs86Aj3fQCdha+UaQvQYLaX3i3O/m7g2bKZ/HsphI4pJx1SLMhhqt/499Sjxnjp 3J62VIOP6o5GPwZ6w6BvaY/L31298UB7s3TLo25Bs2BXdICejZ0Rio0FVWlquChqnvtc fO3g==
X-Gm-Message-State: APjAAAWg3So09nxm950A1011hrBC6+kvfgKc6PAch4LvormuYrwAWr9x NPJIjjS5gKgYp7XB//JWJ27O93FuZCmtV1u7MWA3fKLd1m4=
X-Google-Smtp-Source: APXvYqzbMdhn83hOg6UWqnSy1bZ9M3DxW9dk6JsnasKW7QSS2YWhgj0PrmhnaPvbsI//3mPV1pWu8sOAyayRj+yCvuE=
X-Received: by 2002:a62:1d8a:: with SMTP id d132mr42839853pfd.187.1567550145455; Tue, 03 Sep 2019 15:35:45 -0700 (PDT)
MIME-Version: 1.0
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Tue, 3 Sep 2019 17:35:34 -0500
Message-ID: <CA+YzgTvVJNs31s=WCEuBzLECpm0uYZaa3hjWC_G=dgDbv+Kydw@mail.gmail.com>
To: TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
Content-Type: multipart/alternative; boundary="000000000000966c710591adb58b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/H3azyFI3kIaZDhxwEcSK1_O2CRA>
Subject: [Teas] Network Slicing Design Team - Draft Charter
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: Tue, 03 Sep 2019 22:35:50 -0000

    As discussed in Montreal we are forming a design team to help bring
focus to the many discussions we have been having on Network Slicing.  The
draft objectives and deliverables for the design team are outlined below.
At this time we’d like to ask for comments on this draft -- to be sent to
the WG list.  We would also like to ask any who are interested in
participating in the design team to send the WG chairs (cc’ed above) a
brief note expressing your interest, affiliation and relevant expertise.
Please do so within one week.  We expect the announcement of the DT
formation and membership one week after that.

While we appreciate your interest and willingness to contribute, please be
aware that not all  who volunteer will be included in the team.  All will
be able to participate in this work once we have a WG document on the topic
and, as always, the document progress 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 the 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

TEAS Network Slicing Design Team (Draft)

The topic of “Slicing” has received significant industry attention due to
its planned role in 5G networks.  (General background on slicing can be
found in [1] and [2].) Within the IETF the discussion has largely focused
on “Network Slicing” and to a lesser degree on Service Chaining
implications. [3] provides a sample list of related individual
contributions. Much of this work 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
delivering Network Slicing using existing IETF technologies, and if and
where needed, possible extensions to those technologies - which may be in
the other working groups.  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 from the DT
will be a proposed definition of what is in-scope and what is out-of-scope
for the WG on this topic.

The Design Team will have flexibility to decide on how best to develop,
document and present its work. The DT 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 DT
is an initial DT framework, and possibly draft, in time for discussion at
the meeting.  A stable Draft is targeted for discussion at IETF 108. Once
the draft is accepted as a working group document, it will progress per
TEAS working group normal process.

The DT mailing list will be set up with the membership of this list limited
to the design team and the chairs, but its archive will be open.  DT
meetings will be announced on the list and open to all.  The specific
workings, including meeting schedules, of the DT are the discretion of the
[2] http://www.3gpp.org/ftp//Specs/archive/28_series/28.801/28801-f10.zip
[3] Related IETF drafts