Re: [Paw] Renaming

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 05 April 2019 08:55 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: paw@ietfa.amsl.com
Delivered-To: paw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E111201BE for <paw@ietfa.amsl.com>; Fri, 5 Apr 2019 01:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=fzbGLOJh; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=KMbpBsYa
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 bXlq6Dt_MNTw for <paw@ietfa.amsl.com>; Fri, 5 Apr 2019 01:55:32 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00519120391 for <paw@ietf.org>; Fri, 5 Apr 2019 01:55:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2884; q=dns/txt; s=iport; t=1554454532; x=1555664132; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=xUmcR7dwULOdnmZmN5P89+DjDq0CQVrQm0AgDNc0wZI=; b=fzbGLOJhOmAYqmTZVk6GMclV5d7nf4gwvSOZQpai2Ts9e1ISBJtWMTlP FXmS3nuN2Rs+frf41XFN5acvV91N/KA+BEPGZajbuONmouZAxaWgZmwV5 6A/zOm3jni89F4lLY3AOT+zS8VYH+CEJ1azbBfAAdlue02vkdQgIwG6bR 0=;
IronPort-PHdr: 9a23:wA1QmB0zMncmRD0MsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQEVH7MfTndTASF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CFAACDF6dc/4gNJK1lGgEBAQEBAgEBAQEHAgEBAQGBVAIBAQEBCwGBPVADaFQgBAsnCodLA48mgleXF4JSA1QOAQEgDIRAAoVQIjcGDQEBAwEBCQEDAm0cDIVKAQEBAgI6BgEBKwwBCwQCAQgOAwQBAR8QMh0IAQEEDgUIgxuBXQMVAQIMpBcCihSCIIJ5AQEFgUNDgwIYggwIgTABhF+GVReBQD+BEUaBTn4+gmECAQEBF4FJgzmCJqVwCQKIAIwXlFGRcI1XAgQCBAUCDgEBBYFlIjWBIXAVgycJggGDb4RwhWNyAYEnjigBgR8BAQ
X-IronPort-AV: E=Sophos;i="5.60,312,1549929600"; d="scan'208";a="255509468"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Apr 2019 08:55:30 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x358tUGb026334 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 Apr 2019 08:55:30 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 5 Apr 2019 03:55:29 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 5 Apr 2019 04:55:28 -0400
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 5 Apr 2019 03:55:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rU1FxKIDlPh5D5IioreGfm2CWxMEIbCofvO8mMZkp5s=; b=KMbpBsYaPESKz+TCagj3qAchn8B3wwyujjA35zcp91DQTtgCNFxeX5LM9/1AYa3dE95cLxLC9zT2PIak5Lzd/8G1L2mnCmyBVnLZT4K7kBrLS/n/9KbyBm76otgGDjc2K/yRN1l/ogXFlOxkUcfjSoK56fPPnk0qmNG0qCuYgWo=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3775.namprd11.prod.outlook.com (20.178.253.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.20; Fri, 5 Apr 2019 08:55:26 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::975:4644:7891:e2b1]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::975:4644:7891:e2b1%3]) with mapi id 15.20.1750.017; Fri, 5 Apr 2019 08:55:26 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Juliusz Chroboczek <jch@irif.fr>
CC: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>, Lou Berger <lberger@labn.net>, "paw@ietf.org" <paw@ietf.org>
Thread-Topic: [Paw] Renaming
Thread-Index: AdTquPSJxOwLxttAQ1CFDQj6HPGMsgAPMa2AAAC2ZIAAAjLwcAAPmYqAAA6mZ3A=
Date: Fri, 05 Apr 2019 08:55:02 +0000
Deferred-Delivery: Fri, 5 Apr 2019 08:54:19 +0000
Message-ID: <MN2PR11MB3565F964A5BE9D064758DAF1D8510@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB35656DBEDFAAA662DF39D339D8500@MN2PR11MB3565.namprd11.prod.outlook.com> <d086bbb4-7877-1931-9913-3bc6e01f21b0@labn.net> <311BE885E0DA8D4BB369A037CF5B64A7A0411A3C@ORSMSX107.amr.corp.intel.com> <MN2PR11MB3565EA5719916E0D47BA8CCCD8500@MN2PR11MB3565.namprd11.prod.outlook.com> <87ftqxl4pi.wl-jch@irif.fr>
In-Reply-To: <87ftqxl4pi.wl-jch@irif.fr>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [173.38.220.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 61de13f1-a3c0-443e-274e-08d6b9a47299
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB3775;
x-ms-traffictypediagnostic: MN2PR11MB3775:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <MN2PR11MB3775D925693D88CED60E8486D8510@MN2PR11MB3775.namprd11.prod.outlook.com>
x-forefront-prvs: 0998671D02
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(396003)(136003)(376002)(39860400002)(189003)(199004)(13464003)(106356001)(53936002)(71190400001)(76176011)(486006)(7696005)(71200400001)(25786009)(6246003)(66066001)(11346002)(52536014)(6436002)(6306002)(86362001)(446003)(68736007)(2906002)(6916009)(5660300002)(9686003)(3846002)(256004)(6116002)(97736004)(81166006)(55016002)(93886005)(26005)(74316002)(4326008)(966005)(81156014)(478600001)(6666004)(33656002)(229853002)(54906003)(476003)(99286004)(6506007)(105586002)(316002)(7736002)(305945005)(14454004)(53546011)(186003)(8676002)(8936002)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3775; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: PA8wCrI1P6npFTu4R41sK8GglpjiJIfyyTuAfprv3IKC9nce013hqr4gPPTTV0x2kFydShsqDFVqtS2PNostEZSlcU45FNlxinmet7kFnfFr0mP+pFbpOlGpqS7cUx4UH9v8qBl1+SHGq4/UMefgJou5ldD98zpZkvJlQyItMuv1cL3B6m86B//jp9ugZZTVCtZFF0cwmsGJMw+QB+5LgDQmSd/kcXQEFK36uNoALrULYEaO8eRETb+UQxint1wdGz6X9YtAR8FGsVqv4i01XTn8sPSEnVDbxMg+8H75vj5SA2e9IuRZ5CrCjOXTrwVicBNcdBuyorGpBi0tDaDNwslBSZydhls+Fdae/ArTyw+bM/VNtcYkOPqk0AzNfTRd59cJYj8mw2NginHrsHI6SjgVm9GKnPp5xvfufMVit28=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 61de13f1-a3c0-443e-274e-08d6b9a47299
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2019 08:55:26.6477 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3775
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/27oslnaWH0Jgjj_N1h1lkQFFId0>
Subject: Re: [Paw] Renaming
X-BeenThere: paw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: predictable and available wireless <paw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/paw>, <mailto:paw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/paw/>
List-Post: <mailto:paw@ietf.org>
List-Help: <mailto:paw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/paw>, <mailto:paw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2019 08:55:35 -0000

Hello Juliusz:

Actually the theoretical work has been done a while ago, as  a response to your question at the mike when I suggested you dig for MTBF or similar (MTTF, MTBE...). We tend to express a network form of MTBF in a number of 9s. Like five 9s would indicate that the Mean Successful Transmissions Between Errors is 99999. A number of use cases would thrive on 1% loss as long as losses are always well spaced so the missing points can be recovered. This can be true for an industrial control loop, and false for burning a master video. The N 9s are there to make the occurrence of P (say, 4) losses in a row very rare, like a probability of 1/10^(N*P). But the 9s are for unrelated errors and fail to convey a rare burst of errors with a common cause, which is what really hurts. These things happen on radios and that's why we are after diverse paths etc..

There's enough stats for is in https://ftp.automationdirect.com/pub/Product%20Reliability%20and%20MTBF.pdf to take us a long way. Our problem is to migrate the concept from a product to a sequence of nodes and then to more complex structures. This could be refined in an academic paper, I expect that'd be a great topic, and then an RFC would summarize that.

What I'd like to see is an informational RFC that presents wireless reliability in a way that can be consumed by the IETF members, and provides terminology that can be referred in our specs. You seemed curious about the topic; that's quality number one for achieving great results : )

All the best,

Pascal

More links:
http://www.bb-elec.com/Learning-Center/All-White-Papers/Fiber/MTBF,-MTTR,-MTTF,-FIT-Explanation-of-Terms/MTBF-MTTR-MTTF-FIT-10262012-pdf.pdf
https://books.google.nl/books?id=rNLSBQAAQBAJ&pg=PA171&lpg=PA171&dq=reliability+MTBF+MTBE+papers&source=bl&ots=L7BsInfaO3&sig=ACfU3U0kYd1lGRyRR_aD5AET9LOI8ZfZWg&hl=fr&sa=X&ved=2ahUKEwisr-LirLjhAhWPZ1AKHe8yARwQ6AEwA3oECAgQAQ

https://www.dfrsolutions.com/blog/the-challenges-of-wireless-reliability








> -----Original Message-----
> From: Juliusz Chroboczek <jch@irif.fr>
> Sent: vendredi 5 avril 2019 01:40
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> Cc: Venkatesan, Ganesh <ganesh.venkatesan@intel.com>; Lou Berger
> <lberger@labn.net>; paw@ietf.org
> Subject: Re: [Paw] Renaming
> 
> > We'll also need to provide a definition of reliability and
> > availability and as we discussed, 5nines is probably not the only or
> > even best way to express any of that. Juliusz actually raised the
> > point and I hope he continues on that path and even produces a spec for us.
> 
> I'm flattered you think so, but I'm pretty sure I'm not competent.  You'd need
> someone with more of a background in probability and statistics.
> 
> -- Juliusz