Re: [Teas] Network Slicing Design Team - Draft Charter

Kaippallimalil John <> Wed, 04 September 2019 13:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 002D01200F6; Wed, 4 Sep 2019 06:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1aI8Vgvq_4Nb; Wed, 4 Sep 2019 06:35:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2167B120073; Wed, 4 Sep 2019 06:35:18 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=RN805SKEiDiF8kBWuILh0bVPBAYjod38c5zPfb+LPjZcdydHPjCy2jcJ+3bYvwCu1yoFCKttW4RyQwBYnJhhhpO0D1Og4RZjjBM1OAoRzd1X6wSQjy5GeNKaxoHFuYIX75w241YjgKvqJetLZoikeE7GBNRVsP3raEEqE9JO5ZkF5Vb0KsjgN8JKelu6TVKZutgKiXeSwtI+tpYSVONLHNPS8BlPkJgW8fHUhvsIFFEPYLQRaWTHwNJKKh6AKXPTFEtSfMA6g/cNvln8tAwTt4K7l9gXG5l78QvcilUAX3OqEPQ/PXHX/1kiujumMs8OufPxomh+pncqkpuelKOdXg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=haWI/s4qTN4cugf+wvOSW1Q8/PmV/0siz6HFpeCvkGI=; b=iSQF0C/1UQyHBfMq7S97+Ljxn7+aXBSJQkYDTYpvyqESJ42UhPGtvGDxy9BZLhfRLlrQYSeJ03M6vWQTlcXVFL4MEnjkoXA99b6jK7UBm+NTWWhODZW3Rh4tM3WG2Xylms6TbUgTqt8MB8DLjy9fSzjgmIQmd6CSf80KiNAiTf0jw2+sPVQb3fFeKFZdn7y0HREFe4Xc5ZeWOfE7HyUDtz0YQZ5zPyVCCJByJQ5aTTcr6dtQjdpRSolVyIzR/ZVASb/lBxBPRztYYexk+zwvP0SvofvD+Vu85UriMiqhnEvyN1s5VLGiPzZo4FuuZPUKStCuaI57K3lecNyK2mcibw==
ARC-Authentication-Results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=haWI/s4qTN4cugf+wvOSW1Q8/PmV/0siz6HFpeCvkGI=; b=VbfpdE7D9T9hhZubZfRgD6Rvjx6mJvmuK1Gw6jdQfcZA8QBkb0ewRhDUg7GxDUfGNJOxMNibasIbZTXELbBPeHV8Sv02HBlgI9DifspI6pXTmJMsjB20ALDNJvSEhN+wQJDyBxmkYvtVgC7k9AYa/dLk1+DN9jVANSHwrUV7xoE=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.7; Wed, 4 Sep 2019 13:35:15 +0000
Received: from ([fe80::bc14:e949:9255:465c]) by ([fe80::bc14:e949:9255:465c%6]) with mapi id 15.20.2241.014; Wed, 4 Sep 2019 13:35:15 +0000
From: Kaippallimalil John <>
To: Vishnu Pavan Beeram <>, TEAS WG <>
Thread-Topic: [Teas] Network Slicing Design Team - Draft Charter
Thread-Index: AQHVYqf1LYuNYNxfGk2idNal9zeyUqcbgpNw
Date: Wed, 4 Sep 2019 13:35:14 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: dedf21cb-1bb8-4299-30b0-08d7313cb80b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3375;
x-ms-traffictypediagnostic: MN2PR13MB3375:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0150F3F97D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39850400004)(136003)(396003)(376002)(346002)(366004)(199004)(189003)(99286004)(6246003)(33656002)(6436002)(64756008)(486006)(476003)(110136005)(76116006)(256004)(5024004)(14444005)(66066001)(54906003)(71200400001)(71190400001)(446003)(11346002)(53936002)(316002)(7736002)(25786009)(5660300002)(229853002)(9686003)(236005)(74316002)(55016002)(54896002)(6306002)(66946007)(66556008)(66446008)(66476007)(186003)(86362001)(8936002)(790700001)(478600001)(606006)(14454004)(966005)(8676002)(81156014)(81166006)(102836004)(52536014)(6506007)(76176011)(53546011)(3846002)(26005)(7696005)(2906002)(4326008)(6116002)(15398625002)(19623455009); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3375;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: y0Q1ppCPZakcFjiyOGUy7aa1QTu5ojpEusyOfp5upc2aFSpdcsqp5yL5x/j5WycdNHIWTfE8g4aY705+C0X5dWqrCWi4CY3l0U4muSkwJZJZ9vUwnYbwDQIdtTwHKS6lFpDnbOh4udmMyY5+JhbVhrPH21Vs8IlZUNxdmosCvCTT0qwjtXTrXzvzWlq20ok+zkuX3FbSD5Wd2vmNNyP1xjtsk4AL447LYXq1cB9ozxXuSSKVbyDxvbX+VcnbyZb3POyyogN+s8ANDFn7udIzsAmySe087RPLQ3/YH0wMgaPxp2I+0bsu9LYxgCHR9ZxIiMf8XYjjarqpXJYlq3fo5ULAS4fqodzp+0PphSVRxrYokZSTQ1GS1EoIDugIx93wOAeSNkhpdkgTKnYm9cEfGOAewUmiKh63Z2LkQ0AVJFg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3309E4C067AFEAE18BBAD798E8B80MN2PR13MB3309namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dedf21cb-1bb8-4299-30b0-08d7313cb80b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2019 13:35:14.8736 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 6Yp0fyLuUbkQg9XiEvyXhrD5LbfzbZsRbrrmFthRqx2wKH8MYBO0p1jOHtG2BT0B4i++IIBWrwyPCRXWWngdtA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3375
Archived-At: <>
Subject: Re: [Teas] Network Slicing Design Team - Draft Charter
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Sep 2019 13:35:21 -0000

Pavan, Lou,
For the 3GPP references, TR 28.801 is a technical report and not normative.
Please refer to TS 28.530 - which is a technical specification that covers concepts, use cases and requirements.

Also, please add the following to [3] – Related IETF drafts:


This e-mail and any attachments may contain confidential information from Futurewei, which are intended only for the person or entity whose email address appears above. Any use of the information attached or contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or any unapproved dissemination) by persons other than the intended recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender by phone or response email immediately and delete this original message.

From: Teas <>; On Behalf Of Vishnu Pavan Beeram
Sent: Tuesday, September 03, 2019 5:36 PM
To: TEAS WG <>;
Subject: [Teas] Network Slicing Design Team - Draft Charter

    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 DT.

[3] Related IETF drafts