IETF Logo Mail Archive

Re: [Paw] Renaming after IETF

"Cavalcanti, Dave" <dave.cavalcanti@intel.com> Fri, 08 March 2019 15:57 UTC

Return-Path: <dave.cavalcanti@intel.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 D5D591313E5 for <paw@ietfa.amsl.com>; Fri, 8 Mar 2019 07:57:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 L4zOlX1S3elH for <paw@ietfa.amsl.com>; Fri, 8 Mar 2019 07:57:07 -0800 (PST)
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (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 CB4581313D1 for <paw@ietf.org>; Fri, 8 Mar 2019 07:57:06 -0800 (PST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2019 07:57:06 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.58,456,1544515200"; d="scan'208,217";a="174458446"
Received: from orsmsx110.amr.corp.intel.com ([10.22.240.8]) by orsmga001.jf.intel.com with ESMTP; 08 Mar 2019 07:57:06 -0800
Received: from orsmsx159.amr.corp.intel.com (10.22.240.24) by ORSMSX110.amr.corp.intel.com (10.22.240.8) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 8 Mar 2019 07:57:05 -0800
Received: from orsmsx101.amr.corp.intel.com ([169.254.8.11]) by ORSMSX159.amr.corp.intel.com ([169.254.11.151]) with mapi id 14.03.0415.000; Fri, 8 Mar 2019 07:57:05 -0800
From: "Cavalcanti, Dave" <dave.cavalcanti@intel.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Xavi Vilajosana Guillen <xvilajosana@uoc.edu>, Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
CC: "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "paw@ietf.org" <paw@ietf.org>
Thread-Topic: [Paw] Renaming after IETF
Thread-Index: AdTU/ZLxIAtAC8EWTd6IC4eFjQpZIQAEs4FwAAAdwQAALPtQAAAEuKOAAAQVMCA=
Date: Fri, 08 Mar 2019 15:57:04 +0000
Message-ID: <167E9B9F5274D7459E354580CC4EFD7A41DD337B@ORSMSX101.amr.corp.intel.com>
References: <MN2PR11MB35658225A415C58A5272A961D84C0@MN2PR11MB3565.namprd11.prod.outlook.com> <C3855D43D6701846AD1151A536E7A0584F20EDBA@sjceml521-mbx.china.huawei.com> <C3855D43D6701846AD1151A536E7A0584F20EDEA@sjceml521-mbx.china.huawei.com> <CAC9+vPiDjnYk+LCt-6qHRt+YMo1C+btE8VVtrNkixg2NXvYz0g@mail.gmail.com> <MN2PR11MB3565FED097FB3956B331AC5CD84D0@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB3565FED097FB3956B331AC5CD84D0@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-ctpclassification: CTP_NT
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNDIxODc0OWQtM2UwNy00YTRjLWEwMmEtYTM0ZDBlNDMzOWFmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoicHVTSmNickJTR3UzMm9GQTBoMGpuZWJ4WkJwbTA0TVM2U2o0OTVDb0FKRUt1akJoak0wQmJaYnFBa3hlS0R0aiJ9
x-originating-ip: [10.22.254.138]
Content-Type: multipart/alternative; boundary="_000_167E9B9F5274D7459E354580CC4EFD7A41DD337BORSMSX101amrcor_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/vrRLrRph4ZO7FjR1CSUkKvxxFeE>
Subject: Re: [Paw] Renaming after IETF
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, 08 Mar 2019 15:57:19 -0000

I agree with Pascal on the issues around the term “Deterministic” in wireless, it would be good to avoid it. We can still focus on the same problems.

Thanks
Dave


From: Paw [mailto:paw-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: Friday, March 08, 2019 1:52 AM
To: Xavi Vilajosana Guillen <xvilajosana@uoc.edu>; Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
Cc: int-ads@tools.ietf.org; paw@ietf.org
Subject: Re: [Paw] Renaming after IETF

Guys,

Part of the game is to avoid “Deterministic” because it causes trouble / endless discussions with some Wi-Fi people people would keep telling us that we cannot do determinism on unlicensed bands…
This is why PAW describes the “deterministic” characteristics that we want to enforce, predictability (worst case time delivery) and availability (reliable with redundancy).
For those reasons, I do not think that DAWN is a good idea, sorry… OTOH, the core aspect of HOW we do it is scheduling by a controller. Thus SPAWN.

All the best,

Pascal

From: Xavi Vilajosana Guillen <xvilajosana@uoc.edu<mailto:xvilajosana@uoc.edu>>
Sent: vendredi 8 mars 2019 08:37
To: Hesham ElBakoury <Hesham.ElBakoury@huawei.com<mailto:Hesham.ElBakoury@huawei.com>>
Cc: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>; paw@ietf.org<mailto:paw@ietf.org>; int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>
Subject: Re: [Paw] Renaming after IETF

+1 for DAWN: Deterministic Available Wireless Network.

Missatge de Hesham ElBakoury <Hesham.ElBakoury@huawei.com<mailto:Hesham.ElBakoury@huawei.com>> del dia dj., 7 de març 2019 a les 19:09:
Or perhaps DAWN: Deterministic Available Wireless Network.

From: Paw [mailto:paw-bounces@ietf.org<mailto:paw-bounces@ietf.org>] On Behalf Of Hesham ElBakoury
Sent: Thursday, March 7, 2019 10:07 AM
To: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>; paw@ietf.org<mailto:paw@ietf.org>
Cc: 'int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>' <int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>>
Subject: Re: [Paw] Renaming after IETF

How about DetWN ?
Hesham

From: Paw [mailto:paw-bounces@ietf.org<mailto:paw-bounces@ietf..org>] On Behalf Of Pascal Thubert (pthubert)
Sent: Thursday, March 7, 2019 7:55 AM
To: paw@ietf.org<mailto:paw@ietf.org>
Cc: 'int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>' <int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>>
Subject: [Paw] Renaming after IETF

Dear all:

One comment by the IESG is that the proposed name of PAW is too similar to a that of a past WG called PAWS.
So we’ll need to find a new name. The proposal on the table is SPAWN for “ Scheduled Predictable and Available Wireless Networks”.

Comments / suggestions welcome!

Pascal


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


--
Dr. Xavier Vilajosana
Wireless Networks Lab
Internet Interdisciplinary Institute (IN3)
Professor
(+34) 646 633 681
xvilajosana@uoc.edu<mailto:usuari@uoc.edu>
http://xvilajosana.org
http://wine.rdi.uoc.edu

Parc Mediterrani de la Tecnologia
Av Carl Friedrich Gauss 5, B3 Building
08860 Castelldefels (Barcelona). Catalonia. Spain

[Universitat Oberta de Catalunya]  [https://ferranadelantado.files.wordpress.com/2014/05/wine_logo_small2-e1453363995864.png?w=330&h=123]
­

v2.23.0 | Report a Bug | By Email