IETF Logo Mail Archive

Re: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06

"Wubo (lana)" <lana.wubo@huawei.com> Fri, 01 July 2022 08:59 UTC

Return-Path: <lana.wubo@huawei.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 C26FEC15CF55; Fri, 1 Jul 2022 01:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bv50ZN7qgcjm; Fri, 1 Jul 2022 01:59:27 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C83E0C15D88A; Fri, 1 Jul 2022 01:59:26 -0700 (PDT)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LZ8G05pFVz6F9Bp; Fri, 1 Jul 2022 16:56:56 +0800 (CST)
Received: from kwepemi100012.china.huawei.com (7.221.188.202) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Fri, 1 Jul 2022 10:59:22 +0200
Received: from kwepemi500014.china.huawei.com (7.221.188.232) by kwepemi100012.china.huawei.com (7.221.188.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 1 Jul 2022 16:59:20 +0800
Received: from kwepemi500014.china.huawei.com ([7.221.188.232]) by kwepemi500014.china.huawei.com ([7.221.188.232]) with mapi id 15.01.2375.024; Fri, 1 Jul 2022 16:59:20 +0800
From: "Wubo (lana)" <lana.wubo@huawei.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>
CC: TEAS WG Chairs <teas-chairs@ietf.org>
Thread-Topic: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06
Thread-Index: AQHYis6vsm9HPmw1VE2wyDRXBmRGrq1pOKOg
Date: Fri, 01 Jul 2022 08:59:20 +0000
Message-ID: <478ba7e17a73410e8fe2dd5839da339f@huawei.com>
References: <CA+YzgTs4Z5eEKQfWs19chLxq1bHN0oiRDPfkqWJROsUrNXFnWw@mail.gmail.com>
In-Reply-To: <CA+YzgTs4Z5eEKQfWs19chLxq1bHN0oiRDPfkqWJROsUrNXFnWw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.98.73]
Content-Type: multipart/alternative; boundary="_000_478ba7e17a73410e8fe2dd5839da339fhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/FphccgQENnRGVyKq6WcemgjKrM0>
Subject: Re: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
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, 01 Jul 2022 08:59:30 -0000

Hi WG,

I have read this draft, and I support WG adoption.

I think this use case draft is very useful, as the NS framework defines abstract network slice service concepts and this draft can provide more concrete use cases to describe specific service requirements.

I hope the authors can give some description on why these use cases are consider to be slice services? My understanding is that slice services needs to have specific connection types along with  SLO and SLE requirements. In Sections 4.4 and 4.5, it appears that there is no description of the connection type, detailed SLOs and SLEs requirements, SDP location, etc..

Thanks,
Bo
From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
Sent: Tuesday, June 28, 2022 5:07 PM
To: TEAS WG <teas@ietf.org>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>
Subject: [Teas] WG adoption poll: draft-contreras-teas-slice-nbi-06

All,

This is start of a *two* week poll on making
draft-contreras-teas-slice-nbi-06 a TEAS working group document
[https://datatracker.ietf.org/doc/html/draft-contreras-teas-slice-nbi-06].

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 July 12th.

Thank you,
Pavan and Lou

v2.23.0 | Report a Bug | By Email