IETF Logo Mail Archive

[Netslices] Reliability & Availability in NetSling

"qiangli (D)" <qiangli3@huawei.com> Thu, 10 August 2017 02:04 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 64DA6129A92 for <netslices@ietfa.amsl.com>; Wed, 9 Aug 2017 19:04:21 -0700 (PDT)
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 DSwnzatTGzGu for <netslices@ietfa.amsl.com>; Wed, 9 Aug 2017 19:04:19 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F4FD132518 for <netslices@ietf.org>; Wed, 9 Aug 2017 19:04:18 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMH47839; Thu, 10 Aug 2017 02:04:17 +0000 (GMT)
Received: from DGGEMI405-HUB.china.huawei.com (10.3.17.143) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 10 Aug 2017 03:04:16 +0100
Received: from DGGEMI509-MBS.china.huawei.com ([169.254.2.103]) by dggemi405-hub.china.huawei.com ([10.3.17.143]) with mapi id 14.03.0301.000; Thu, 10 Aug 2017 10:04:10 +0800
From: "qiangli (D)" <qiangli3@huawei.com>
To: "netslices@ietf.org" <netslices@ietf.org>
Thread-Topic: Reliability & Availability in NetSling
Thread-Index: AdMRfN5eHIJHr9ZeRXW5IRXAHZDYnQ==
Date: Thu, 10 Aug 2017 02:04:09 +0000
Message-ID: <06C389826B926F48A557D5DB5A54C4ED2A5743F7@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_06C389826B926F48A557D5DB5A54C4ED2A5743F7dggemi509mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.598BBF21.00E6, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.103, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: cf44b3a38bd0ff7effb5bdb6c32e8d45
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/8gLXYJk-ruGArzpGrO9tjQP17gc>
Subject: [Netslices] Reliability & Availability in NetSling
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: Thu, 10 Aug 2017 02:04:21 -0000

Hi All,

I was confused when I was reading some NetSlicing related materials. It seems that "Reliability" supported by Netslicing refers to the probability that a network slice could work stably, or other similar metrics. But, shouldn't this be the defination of "Availability"? Then what does reliability mean in NetSlicing?


Best regards,

Cristina QIANG

v2.23.0 | Report a Bug | By Email