Re: [Paw] Renaming after IETF

"Shankar Ramanathan (shankram)" <shankram@cisco.com> Fri, 08 March 2019 16:44 UTC

Return-Path: <shankram@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 377101313FA for <paw@ietfa.amsl.com>; Fri, 8 Mar 2019 08:44:07 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, 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, 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
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 U10f9Z861e_o for <paw@ietfa.amsl.com>; Fri, 8 Mar 2019 08:44:05 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D475112797D for <paw@ietf.org>; Fri, 8 Mar 2019 08:44:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=32312; q=dns/txt; s=iport; t=1552063444; x=1553273044; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ENm9WgChwMs6d3nkNbpXGXptZacQ9V2i04E9wq4hyqc=; b=EBelrG1uAa31D5xKoDuZROsTY4q/eC0ptMw5+giibJ2FcFvswJdxHKhi RmxzfGxM/RUykb+o1vrerCRdkx7IluLTAbDhsLh7GziPw/gEVyjuxxPmA fHLFUOm3D9ZG94ymteu8mp+8hgnaG9pMsBgFWXKnIrD0zjA2MjtA9QaNS 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAClmoJc/4cNJK1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ2BAmiBAycKg3+IGo07gwiVHhSBZwsBARgBCoRJAheEHiI0CQ0BAQMBAQcBAwJtHAyFSgEBAQQBASEKQQsQAgEIEQMBAQEhBwMCAgIlCxQJCAIEAQ0FCIMbgRFkD6pkgS+KLYEvAYsrF4FAP4ERgxKDHgEBgSlGCQkWCIJMglcCiXaBJoEDKoQIHpMvCQKHTYVnhUshglCQaIp3hWOMXgIRFIEoDRI4gVZwFTuCbAmGWYQqhT9BMQGOeIEfAQE
X-IronPort-AV: E=Sophos;i="5.58,456,1544486400"; d="scan'208,217";a="530062063"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2019 16:44:03 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x28Gi3m8010717 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 8 Mar 2019 16:44:03 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 8 Mar 2019 10:44:02 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1473.003; Fri, 8 Mar 2019 10:44:02 -0600
From: "Shankar Ramanathan (shankram)" <shankram@cisco.com>
To: "Georgios Z. Papadopoulos" <georgios.papadopoulos@imt-atlantique.fr>, "Jerome Henry (jerhenry)" <jerhenry@cisco.com>
CC: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Xavi Vilajosana Guillen <xvilajosana@uoc.edu>, "Cavalcanti, Dave" <dave.cavalcanti@intel.com>, Hesham ElBakoury <Hesham.ElBakoury@huawei.com>, "paw@ietf.org" <paw@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>
Thread-Topic: [Paw] Renaming after IETF
Thread-Index: AdTU/ZLxIAtAC8EWTd6IC4eFjQpZIQAEs4FwAAAdwQAAKMpuAAAEuKKAAAy+UAAAACHTgAABKxEAAAw/08A=
Date: Fri, 08 Mar 2019 16:44:02 +0000
Message-ID: <a7cb7ddfd7b84461bb55bf455ef65a08@XCH-ALN-001.cisco.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> <167E9B9F5274D7459E354580CC4EFD7A41DD337B@ORSMSX101.amr.corp.intel.com> <2E1B596A-82C8-4DA1-A4B0-C7E4138FC68D@cisco.com> <CD3BB4BD-6C76-44E9-82F3-A6AAF6E2BA4E@imt-atlantique.fr>
In-Reply-To: <CD3BB4BD-6C76-44E9-82F3-A6AAF6E2BA4E@imt-atlantique.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.99.55.103]
Content-Type: multipart/alternative; boundary="_000_a7cb7ddfd7b84461bb55bf455ef65a08XCHALN001ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/8NRiB3oh5LOU9ywYHkIZk8b8080>
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 16:44:07 -0000

SPAWN



--
Shankar

From: Paw <paw-bounces@ietf.org> On Behalf Of Georgios Z. Papadopoulos
Sent: Friday, March 08, 2019 10:34 AM
To: Jerome Henry (jerhenry) <jerhenry@cisco.com>
Cc: Pascal Thubert (pthubert) <pthubert@cisco.com>; Xavi Vilajosana Guillen <xvilajosana@uoc.edu>; Cavalcanti, Dave <dave.cavalcanti@intel.com>; Hesham ElBakoury <Hesham.ElBakoury@huawei.com>; paw@ietf.org; int-ads@tools.ietf.org
Subject: Re: [Paw] Renaming after IETF

1+ for SPAWN,
Georgios


On Mar 8, 2019, at 17:00, Jerome Henry (jerhenry) <jerhenry@cisco.com<mailto:jerhenry@cisco.com>> wrote:

+1 for SPAWN.

Putting the word ‘deterministic’ is like telling security guys of an ‘unbreakable’ security scheme, guaranteed to be an endless source of argument…

Jerome


From: Paw <paw-bounces@ietf.org<mailto:paw-bounces@ietf.org>> on behalf of "Cavalcanti, Dave" <dave.cavalcanti@intel.com<mailto:dave.cavalcanti@intel.com>>
Date: Friday, March 8, 2019 at 10:58 AM
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>>, Xavi Vilajosana Guillen <xvilajosana@uoc.edu<mailto:xvilajosana@uoc.edu>>, Hesham ElBakoury <Hesham.ElBakoury@huawei.com<mailto:Hesham.ElBakoury@huawei.com>>
Cc: "int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>" <int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>>, "paw@ietf.org<mailto:paw@ietf.org>" <paw@ietf.org<mailto:paw@ietf.org>>
Subject: Re: [Paw] Renaming after IETF

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<mailto:xvilajosana@uoc.edu>>; Hesham ElBakoury <Hesham.ElBakoury@huawei.com<mailto:Hesham.ElBakoury@huawei.com>>
Cc: int-ads@tools.ietf.org<mailto:int-ads@tools.ietf.org>; paw@ietf.org<mailto: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://xvilajosana.org/>
http://wine.rdi.uoc.edu<http://wine.rdi.uoc.edu/>

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


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