Re: [Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition

peng.shaofu@zte.com.cn Fri, 15 January 2021 02:08 UTC

Return-Path: <peng.shaofu@zte.com.cn>
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 1F1253A0408; Thu, 14 Jan 2021 18:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 i52ZmZbNsLBn; Thu, 14 Jan 2021 18:08:44 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12B893A03FB; Thu, 14 Jan 2021 18:08:43 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.215]) by Forcepoint Email with ESMTPS id 3D0E3BBE5C6E967CBBB8; Fri, 15 Jan 2021 10:08:39 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 1B61C29C5AE6E70B0961; Fri, 15 Jan 2021 10:08:39 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id 10F28TC3017367; Fri, 15 Jan 2021 10:08:29 +0800 (GMT-8) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Fri, 15 Jan 2021 10:08:29 +0800 (CST)
Date: Fri, 15 Jan 2021 10:08:29 +0800 (CST)
X-Zmail-TransId: 2afd6000f91d48fa6ffb
X-Mailer: Zmail v1.0
Message-ID: <202101151008295415129@zte.com.cn>
In-Reply-To: <CA+YzgTuJWXENUQLHrFeYWga1XumA4cf1Gr7DgqXw74fxvz-FNQ@mail.gmail.com>
References: CA+YzgTuJWXENUQLHrFeYWga1XumA4cf1Gr7DgqXw74fxvz-FNQ@mail.gmail.com
Mime-Version: 1.0
From: <peng.shaofu@zte.com.cn>
To: <vishnupavan@gmail.com>
Cc: <teas@ietf.org>, <teas-chairs@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 10F28TC3017367
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/TZcpm5WfDxZadjWjTp9KgvSzQgI>
Subject: Re: [Teas] =?utf-8?q?WG_adoption_-_draft-nsdt-teas-ietf-network-slic?= =?utf-8?q?e-definition?=
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: Fri, 15 Jan 2021 02:08:46 -0000

A little comment:






It seems that the definition document only support that the realization of IETF network slice is triggered by the consumer through the interface to NSC with specific SLO. I think it is not enough. Please see if it is needed to support the case for a network device (the headend) to explicitly request a slice on demand, and request a connection path within the specific slice on demand.






Regards,


PSF







原始邮件



发件人:VishnuPavanBeeram
收件人:TEAS WG;
抄送人:TEAS WG Chairs;
日 期 :2021年01月04日 22:02
主 题 :[Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition


_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas


All,
 
 This is start of a two week poll on making
draft-nsdt-teas-ietf-network-slice-definition-02 a TEAS working group document.
 Please send email to the list indicating "yes/support" or "no/do not
 support". If indicating no, please state your reservations with the
 document. If yes, please also feel free to provide comments you'd
 like to see addressed once the document is a WG document.
 
 The poll ends January 18th.
 
 Thanks,
 Pavan and Lou