[Paw] RAW it is

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 15 April 2019 12: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 365BE120177 for <paw@ietfa.amsl.com>; Mon, 15 Apr 2019 05:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.49
X-Spam-Level:
X-Spam-Status: No, score=-14.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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=lJaAEjsC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=MRzDACQP
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 7Uc41FWEbg5x for <paw@ietfa.amsl.com>; Mon, 15 Apr 2019 05:55:29 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DB0F120143 for <paw@ietf.org>; Mon, 15 Apr 2019 05:55:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=30244; q=dns/txt; s=iport; t=1555332929; x=1556542529; h=from:to:cc:subject:date:message-id:mime-version; bh=dy9Li3/grsDUHudCg6c0tx7xqQqEpdJD+eiOxRGOQxQ=; b=lJaAEjsCTJ6+wy9PYsqpQu/dA+7T6aS8Qq7PuadDYSt0DiRx6o9i7swA F0ffYtHHmGsA+z27jyLmK3LhLC+yZp+WzUiMcdyS/eU4+JS4dm+mjFait 5x4b/5oAvrXkf+oVvlq8Yd8CubDJbScB19R3GBeLiaO91+sCnkDdid1I1 I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AlLRlqRY57lNcx8nZmSL9HfT/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavycywnFslYSHdu/mqwNg5eH8OtL1A=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAAAhfrRc/4ENJK1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBZYEPL1ADaFUgBAsohA6DRwOPFIJXlxqBQoEQA1QOAQEYAQc?= =?us-ascii?q?NhEACF4VtIzgTAQMBAQoBAgECbRwBC4VKAQEBAgECASEKEwEBByQBCwEEBwY?= =?us-ascii?q?BGQQBASEHAwIEJQsUCQkBBA4FCIMbgR1MAw0PAQIMmFgCihRxgS+CeQEBBYF?= =?us-ascii?q?EQ4JyGIINCYEyhGGGaReBQD+BEUaBToQdAQEBAQEXgQ8YAQEgBQcfCQiCTDG?= =?us-ascii?q?CJo0phDkeh0SMcQkCggWGCYEnhHWGDIIIkmuLZoYsjW8CBAIEBQIOAQEFgWY?= =?us-ascii?q?hNYEhcBU7gmwJggGDXRKEcCSFP3IBgSiNBoJDAQE?=
X-IronPort-AV: E=Sophos;i="5.60,353,1549929600"; d="scan'208,217";a="259053684"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Apr 2019 12:55:28 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x3FCtRhC020927 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 15 Apr 2019 12:55:28 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 15 Apr 2019 07:55:27 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 15 Apr 2019 07:55:26 -0500
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 15 Apr 2019 08:55:26 -0400
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=dy9Li3/grsDUHudCg6c0tx7xqQqEpdJD+eiOxRGOQxQ=; b=MRzDACQPT3gIE98EM5iGbCKZrwhXwlWXFXcPQCKri4wbtiAu86WgOQHR+hVqQXl3IjLWb4wVWQ+fYOeHlmiAuppWI9Pjg/eF4tu4VvdZbUGKszU7NGxnfl3ZgblXNLKewzJfO76ua5wZ0M3fd8hL+RwzPiF+IAUQIEKEA1wP1K8=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3839.namprd11.prod.outlook.com (20.178.254.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.19; Mon, 15 Apr 2019 12:55:25 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::8cde:9e01:ad20:d10e]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::8cde:9e01:ad20:d10e%6]) with mapi id 15.20.1792.018; Mon, 15 Apr 2019 12:55:25 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "paw@ietf.org" <paw@ietf.org>
CC: Lou Berger <lberger@labn.net>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Thread-Topic: RAW it is
Thread-Index: AdTzijrNiOZW09+XTPuqBod+QbGnpQ==
Date: Mon, 15 Apr 2019 12:55:02 +0000
Deferred-Delivery: Mon, 15 Apr 2019 12:54:33 +0000
Message-ID: <MN2PR11MB35656DCC6282924B7ECA3720D82B0@MN2PR11MB3565.namprd11.prod.outlook.com>
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: [2001:420:44f3:1300:552f:ff32:b86:aad7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 919b9afb-da4e-41c1-0388-08d6c1a1a0f3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB3839;
x-ms-traffictypediagnostic: MN2PR11MB3839:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <MN2PR11MB3839C957B9924DF34292F480D82B0@MN2PR11MB3839.namprd11.prod.outlook.com>
x-forefront-prvs: 000800954F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(39860400002)(376002)(396003)(136003)(13464003)(199004)(189003)(99286004)(6506007)(53386004)(6306002)(14444005)(256004)(476003)(66574012)(54896002)(46003)(55016002)(74316002)(236005)(316002)(7696005)(186003)(53936002)(5070765005)(6436002)(2351001)(53546011)(966005)(102836004)(68736007)(8936002)(4326008)(9686003)(7736002)(478600001)(2906002)(790700001)(105586002)(106356001)(606006)(14454004)(5660300002)(1730700003)(81166006)(54906003)(2501003)(6666004)(25786009)(71190400001)(71200400001)(486006)(86362001)(81156014)(7116003)(52536014)(6116002)(8676002)(3480700005)(5640700003)(6916009)(97736004)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3839; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: e8fbI4XokHiI3KKYka+/kKZZLJ/TOfKEBLDx/l3417+OAsECw8HlVRcyxxHu0jkiubhOEKvxgsIAiJsnBxergDHnLuUsdSbfzLjqJsQxRGdjOOYAeLmL98/oDvOVNAiutfENQ65kXW+WjezQRE6bJhn+/flmoUhtRRQcTJSVnwRa7+UjQluOw8397W/dJUAYtPusorKDjmqJZCq60lo2Q/EdBvurdHDd81slmM6dSyRtnuAF8BX6w4pRacPwspgWoaqxM9w9L7EH0qZDLQKNijfjgKfnkTN5UiGG9Mf8zKnl/gpHYTCz2EBYC0vMSVuC6WR7W3mTZLob3UYdkCjTeMp8WVGaEuE7o6/L6zW3UIDMEoC2MQcoTW3oChkd/uOiaC0NZ7GA8D0PfCeLtrmOPw/vpEN5m03BLjQQHDwt/Uk=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35656DCC6282924B7ECA3720D82B0MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 919b9afb-da4e-41c1-0388-08d6c1a1a0f3
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2019 12:55:25.1638 (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: MN2PR11MB3839
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/pV7MVQCVLJR-yviiyfqKY3H11KE>
Subject: [Paw] RAW it is
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: Mon, 15 Apr 2019 12:55:33 -0000

Dear all:

There was a strong consensus for RAW. I consider the name adopted, and will work the next phase with the IESG secretary.

All the best,

Pascal

From: Pascal Thubert (pthubert)
Sent: vendredi 5 avril 2019 19:59
To: Prof. Diego Dujovne <diego.dujovne@mail.udp.cl>cl>; Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
Cc: Lou Berger <lberger@labn.net>et>; paw@ietf.org; Venkatesan, Ganesh <ganesh.venkatesan@intel.com>om>; Juliusz Chroboczek <jch@irif.fr>
Subject: RE: [Paw] Renaming: SPAWN vs. RAW

Votes are still open. Do we keep SPAWN or do we jump to RAW.
What does sound right, a SPAWN or a RAW Network?

All the best,

Pascal

From: Paw <paw-bounces@ietf.org<mailto:paw-bounces@ietf.org>> On Behalf Of Prof. Diego Dujovne
Sent: vendredi 5 avril 2019 13:51
To: Hesham ElBakoury <Hesham.ElBakoury@huawei.com<mailto:Hesham.ElBakoury@huawei.com>>
Cc: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>; Lou Berger <lberger@labn.net<mailto:lberger@labn.net>>; paw@ietf.org<mailto:paw@ietf.org>; Venkatesan, Ganesh <ganesh.venkatesan@intel.com<mailto:ganesh.venkatesan@intel.com>>; Juliusz Chroboczek <jch@irif.fr<mailto:jch@irif.fr>>
Subject: Re: [Paw] Renaming

Pascal,
           Shall we split this e-mail between the renaming
topic and the reliability metrics discussion? I think both
items are really relevant to the group and deserve their
individual space.
Regards,

                             Diego Dujovne

Le ven. 5 avr. 2019 à 07:03, Hesham ElBakoury <Hesham.ElBakoury@huawei.com<mailto:Hesham.ElBakoury@huawei.com>> a écrit :

There is a good book on reliability by Michael Tortorella. The book is "Reliability, Maintainability, and Supportability: Best Practices for Systems Engineers". It is available from Wiley.

Hesham



-----Original Message-----
From: Paw [mailto:paw-bounces@ietf.org<mailto:paw-bounces@ietf.org>] On Behalf Of Pascal Thubert (pthubert)
Sent: Friday, April 5, 2019 1:55 AM
To: Juliusz Chroboczek <jch@irif.fr<mailto:jch@irif.fr>>
Cc: Lou Berger <lberger@labn.net<mailto:lberger@labn.net>>; paw@ietf.org<mailto:paw@ietf.org>; Venkatesan, Ganesh <ganesh.venkatesan@intel.com<mailto:ganesh.venkatesan@intel.com>>
Subject: Re: [Paw] Renaming



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<https://www..dfrsolutions.com/blog/the-challenges-of-wireless-reliability>

















> -----Original Message-----

> From: Juliusz Chroboczek <jch@irif.fr<mailto:jch@irif.fr>>

> Sent: vendredi 5 avril 2019 01:40

> To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>

> Cc: Venkatesan, Ganesh <ganesh.venkatesan@intel.com<mailto:ganesh.venkatesan@intel.com>>; Lou Berger

> <lberger@labn.net<mailto:lberger@labn.net>>; paw@ietf.org<mailto: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



--

Paw mailing list

Paw@ietf.org<mailto:Paw@ietf.org>

https://www.ietf..org/mailman/listinfo/paw<https://www..ietf.org/mailman/listinfo/paw>
--
Paw mailing list
Paw@ietf.org<mailto:Paw@ietf.org>
https://www.ietf.org/mailman/listinfo/paw


--
DIEGO DUJOVNE
Profesor Asociado
Escuela de Informática y Telecomunicaciones
Facultad de Ingeniería - Universidad Diego Portales - Chile
www.ingenieria.udp.cl<http://www.ingenieria.udp.cl>
(56 2) 676 8125