IETF Logo Mail Archive

Re: [Paw] Renaming after IETF

Hesham ElBakoury <Hesham.ElBakoury@huawei.com> Thu, 07 March 2019 18:09 UTC

Return-Path: <Hesham.ElBakoury@huawei.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 953A0127983 for <paw@ietfa.amsl.com>; Thu, 7 Mar 2019 10:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 QZncoBadNx4d for <paw@ietfa.amsl.com>; Thu, 7 Mar 2019 10:09:35 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 D9FF4127817 for <paw@ietf.org>; Thu, 7 Mar 2019 10:09:34 -0800 (PST)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id BEBB5EEA76BA4FA19894 for <paw@ietf.org>; Thu, 7 Mar 2019 18:09:32 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 7 Mar 2019 18:09:32 +0000
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.96]) by SJCEML701-CHM.china.huawei.com ([169.254.3.135]) with mapi id 14.03.0415.000; Thu, 7 Mar 2019 10:09:24 -0800
From: Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
To: Hesham ElBakoury <Hesham.ElBakoury@huawei.com>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "paw@ietf.org" <paw@ietf.org>
CC: "'int-ads@tools.ietf.org'" <int-ads@tools.ietf.org>
Thread-Topic: Renaming after IETF
Thread-Index: AdTU/ZLxIAtAC8EWTd6IC4eFjQpZIQAEs4FwAAAdwQA=
Date: Thu, 07 Mar 2019 18:09:23 +0000
Message-ID: <C3855D43D6701846AD1151A536E7A0584F20EDEA@sjceml521-mbx.china.huawei.com>
References: <MN2PR11MB35658225A415C58A5272A961D84C0@MN2PR11MB3565.namprd11.prod.outlook.com> <C3855D43D6701846AD1151A536E7A0584F20EDBA@sjceml521-mbx.china.huawei.com>
In-Reply-To: <C3855D43D6701846AD1151A536E7A0584F20EDBA@sjceml521-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.212.245.231]
Content-Type: multipart/alternative; boundary="_000_C3855D43D6701846AD1151A536E7A0584F20EDEAsjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/wHvJL95NnVw3tLoju_fywAvOwJ8>
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: Thu, 07 Mar 2019 18:09:36 -0000

Or perhaps DAWN: Deterministic Available Wireless Network.

From: Paw [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>; paw@ietf.org
Cc: 'int-ads@tools.ietf.org' <int-ads@tools.ietf.org>
Subject: Re: [Paw] Renaming after IETF

How about DetWN ?
Hesham

From: Paw [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' <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

v2.23.0 | Report a Bug | By Email