IETF Logo Mail Archive

[Netslices] Open Issue II: Service Model

"qiangli (D)" <qiangli3@huawei.com> Wed, 13 December 2017 08:48 UTC

Return-Path: <qiangli3@huawei.com>
X-Original-To: netslices@ietfa.amsl.com
Delivered-To: netslices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FAC612700F for <netslices@ietfa.amsl.com>; Wed, 13 Dec 2017 00:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 FDqDIRCagDdQ for <netslices@ietfa.amsl.com>; Wed, 13 Dec 2017 00:48:06 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 958FB120726 for <NetSlices@ietf.org>; Wed, 13 Dec 2017 00:48:06 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id CC10D96280DB8 for <NetSlices@ietf.org>; Wed, 13 Dec 2017 08:48:03 +0000 (GMT)
Received: from DGGEMI422-HUB.china.huawei.com (10.1.199.151) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 13 Dec 2017 08:48:05 +0000
Received: from DGGEMI509-MBS.china.huawei.com ([169.254.2.152]) by dggemi422-hub.china.huawei.com ([10.1.199.151]) with mapi id 14.03.0361.001; Wed, 13 Dec 2017 16:48:02 +0800
From: "qiangli (D)" <qiangli3@huawei.com>
To: "NetSlices@ietf.org" <NetSlices@ietf.org>
Thread-Topic: Open Issue II: Service Model
Thread-Index: AdNz7kglBMJ4YdSDRSKfDHJYjsVJXg==
Date: Wed, 13 Dec 2017 08:48:02 +0000
Message-ID: <06C389826B926F48A557D5DB5A54C4ED2A5DEDB3@dggemi509-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.163.138]
Content-Type: multipart/alternative; boundary="_000_06C389826B926F48A557D5DB5A54C4ED2A5DEDB3dggemi509mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/TUN373HSrHbeFiJ0N0WS7OhN-qs>
Subject: [Netslices] Open Issue II: Service Model
X-BeenThere: netslices@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is intended for discussion and review of network slicing at IETF." <netslices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netslices>, <mailto:netslices-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netslices/>
List-Post: <mailto:netslices@ietf.org>
List-Help: <mailto:netslices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netslices>, <mailto:netslices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 08:48:08 -0000

Hi All,

This email is trying to collect your opinion on the following issue:

Do we need a COMS Service Model? Or do you think current L2SM/L3SM/etc. is enough to support the resource-oriented (including connectivity, computing, storage and other potential resources) common management on network slices?

Best regards,

Cristina QIANG

v2.23.0 | Report a Bug | By Email