IETF Logo Mail Archive

Re: [Netslices] Reliability & Availability in NetSling

GENG Liang <liang.geng@hotmail.com> Thu, 10 August 2017 02:44 UTC

Return-Path: <liang.geng@hotmail.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 69C94127735 for <netslices@ietfa.amsl.com>; Wed, 9 Aug 2017 19:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.124
X-Spam-Level:
X-Spam-Status: No, score=-1.124 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
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 6ezuzmXTkLCG for <netslices@ietfa.amsl.com>; Wed, 9 Aug 2017 19:44:17 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255011.outbound.protection.outlook.com [40.92.255.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1339D13252B for <netslices@ietf.org>; Wed, 9 Aug 2017 19:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=72VQbnXL//ZW0LUEc5jKQ1qwPaSlzODHFRZGyCpbUXQ=; b=cSYtZDe8JW9c2igHjiU2yLtoKCDdCbZw7aMkk6XJxGE77Ijz96r7zFom42VSKpgxonQpYXJ9ljq93Hr7VwtOxQ/UY49e6X4IEEKzbH0Zzkp5O4yKlSVDA4QNuqRMJ615Zxc9CJRqwhhdnqxBqORhfCWNXRqgT5rGf64jQxdLP1Kw1aJYv6n2Ox0dqvc3ZXtHkE0tEl5AJK8EUC7NVK4611X3Gm02nDtWf7pLWLFgdm3OqK/317MQR6oCMReK3SLRZYSdO2gGQVH3sEKqCddArrKqUSaJEhpld8TKuVk6XxmwH5mYH+diyC7S7rQSuAUrGIQzkYeW1ygBmeqmGVXSAA==
Received: from PU1APC01FT015.eop-APC01.prod.protection.outlook.com (10.152.252.56) by PU1APC01HT087.eop-APC01.prod.protection.outlook.com (10.152.253.120) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1282.16; Thu, 10 Aug 2017 02:44:09 +0000
Received: from TY1PR06MB0928.apcprd06.prod.outlook.com (10.152.252.52) by PU1APC01FT015.mail.protection.outlook.com (10.152.252.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1304.16 via Frontend Transport; Thu, 10 Aug 2017 02:44:09 +0000
Received: from TY1PR06MB0928.apcprd06.prod.outlook.com ([10.164.99.154]) by TY1PR06MB0928.apcprd06.prod.outlook.com ([10.164.99.154]) with mapi id 15.01.1320.018; Thu, 10 Aug 2017 02:44:09 +0000
From: GENG Liang <liang.geng@hotmail.com>
To: "'qiangli (D)'" <qiangli3@huawei.com>, "netslices@ietf.org" <netslices@ietf.org>
Thread-Topic: [Netslices] Reliability & Availability in NetSling
Thread-Index: AdMRfN5eHIJHr9ZeRXW5IRXAHZDYnQ==
Date: Thu, 10 Aug 2017 02:44:09 +0000
Message-ID: <TY1PR06MB0928FED40F8D136737C6036187880@TY1PR06MB0928.apcprd06.prod.outlook.com>
References: <06C389826B926F48A557D5DB5A54C4ED2A5743F7@dggemi509-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:12AE0646F5F32CFBDC4300116D3AE1395742B19C04ADD97371E4CFF0413B72B6; UpperCasedChecksum:2CBBF21FC8931D5441ACB680A4CB0252472B06CDE6B144B13F2E929917B23FA8; SizeAsReceived:7207; Count:45
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [35ekOk4ha329FZg18Gf59cVyZ+GLUn7j]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT087; 7:uPq3Osg7GKKfhbJccsbCdJP9opL4/aVfXteWM43HzvAWfG3s3Kq291DJgWQ6j1CS8cXqjLdHOkeU+CcaVlU5VbJiUO0mDlbQkL1bWXwL42jF64LQ3HjCYMgRVxJXvvGWTGTmusm7Nlg304pfbxHK3+RQaHjM+2RASJahY+ILhAJWYytYaSdX7HWZ3zdIB/V5nsD256XLLM0wT7c4y7murq2Jd12OOd1M49hszfjqgpzLXane8VBngygZUjQwJhVc8QQxMNQytbdPUzYLX0MZtND/gaM1o0mW9Oexhk5MqMiK+yd6ZvclTOCkdpcF0yCGh5GDN0FLRSmpMnMvrjpk3e5QDB0g5TkiXt09Lfz3XvvtByLlZgjDK5sekReQ9GaGICKKIZcWjFWl7Vjs/1aNe61f8Hokdhcm8U7aLAkNPQRqgcSfdbUmYrGQmiSAe6vZ7WZI1XuYO717ZjEZ1gKLaAFqXLqI3/dKKk6bG1vDhkls/fXHiAyqDswFQB2A/opkNOdyLk0Fjlh0pV8UOe1AFcysc/U/iTxLdz46o1loULa6f70wnGdESB/qegON7ZuTUk0CLTNFTc9DCcEBd44WohXX2dPhIkV/qMxFJjLtcjql2AbIjxHvYsj4oWB51dglYNMJvKSkJE9KVuKI5nW0CP7hZFK1o/zKtFvDCgqn2qSv3kv5ReYycctFtoGEQhjkFDWWrrsGrOahoOGo3thcysPFfIFcIFy5JaA6vCGZs4ChAV3dC1iKRKzGfJFfV+SJCyfz2skKDLR2Qz7uA0jj7Q==
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:PU1APC01HT087; H:TY1PR06MB0928.apcprd06.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: 20a999b1-f22d-4442-0d27-08d4df99ac9f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322377)(1603101448)(1601125374)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:PU1APC01HT087;
x-ms-traffictypediagnostic: PU1APC01HT087:
x-exchange-antispam-report-test: UriScan:(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:PU1APC01HT087; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PU1APC01HT087;
x-forefront-prvs: 03950F25EC
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_TY1PR06MB0928FED40F8D136737C6036187880TY1PR06MB0928apcp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Aug 2017 02:44:09.2521 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT087
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/-1-ItTJE1x9E6Zxjr6QXtYKmeQM>
Subject: Re: [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:44:18 -0000

Hi Cristina,

Interestingly we were discussing this confusion with few industrial partners recently. In telecommunication language we normally use "Reliability" to refer the probability a network is stably run (i.e. 99.999% of time). This is also regarded as network "Availability". However, "Reliability" in industrial verticals is more comprehensive - including not only network availability parameter but also mechanics, electricity etc.

Personally I think, network slicing is still looking at network regime where I believe Reliability means the percentage of time a connection is available. But we you sell this concept to industrial verticals, they may think differently.

________________________________
Liang GENG
China Mobile Research Institute

From: qiangli (D)<mailto:qiangli3@huawei.com>
Date: 2017-08-10 10:04
To: netslices@ietf.org<mailto:netslices@ietf.org>
Subject: [Netslices] Reliability & Availability in NetSling
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