Re: [Paw] Renaming

"Pascal Thubert (pthubert)" <> Thu, 04 April 2019 16:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 63C141200DE for <>; Thu, 4 Apr 2019 09:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.5
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: (amavisd-new); dkim=pass (1024-bit key) header.b=QxLne2CE; dkim=pass (1024-bit key) header.b=fGaOxi3l
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R6WYL3ScbNyQ for <>; Thu, 4 Apr 2019 09:31:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 76F7812007A for <>; Thu, 4 Apr 2019 09:31:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=5552; q=dns/txt; s=iport; t=1554395511; x=1555605111; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=aY/00gB9EMy5+2UNinlMAuI+paGc5dq1njicQvBcATk=; b=QxLne2CE0Dpgap0YJGv/xaObeSQPknx1WQydQf23UN3ADXdzNhr9y3iF mC5Fg94hF6heRDeLQaK6o4O2ofzOW1r8ajsZ/bIvCupE7QSWEC043p3ZE /yAAeCaq5ZgxNeBIJ7kL9zeNRlAB8pwpLB3CgczUcyGGidK94KiGWC7QH o=;
IronPort-PHdr: 9a23:kEkwyxEsyZtwNQkuynq/4p1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+eeb2bzEwEd5efFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.60,308,1549929600"; d="scan'208";a="255252424"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Apr 2019 16:31:50 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id x34GVof4001947 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Apr 2019 16:31:50 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 11:31:49 -0500
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 4 Apr 2019 12:31:48 -0400
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 4 Apr 2019 11:31:48 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VfIQBp2iPlepduaxvhkbYq70DNPSTca86DfTFt1aN1Q=; b=fGaOxi3lYqAxO0pbLpjs01Ist9tG74LJCUg1f35HsDSAkp/gUJQ8YTU3d7IJOwubp6L8UjcR3uw9DB0X1svxe44kssfX7MSEY4NAzBuaUs1+g+SJNGoJPhwVeHoMx4OV99uhlJa9a1zvkGwYKFYyX9dB+pLuU9rpSY4DOtWf/wI=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.15; Thu, 4 Apr 2019 16:31:46 +0000
Received: from ([fe80::975:4644:7891:e2b1]) by ([fe80::975:4644:7891:e2b1%3]) with mapi id 15.20.1750.017; Thu, 4 Apr 2019 16:31:46 +0000
From: "Pascal Thubert (pthubert)" <>
To: "Venkatesan, Ganesh" <>, Lou Berger <>, "" <>, 'Juliusz Chroboczek' <>
Thread-Topic: [Paw] Renaming
Thread-Index: AdTquPSJxOwLxttAQ1CFDQj6HPGMsgAPMa2AAAC2ZIAAAjLwcA==
Date: Thu, 04 Apr 2019 16:31:44 +0000
Deferred-Delivery: Thu, 4 Apr 2019 16:31:32 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 93a9f29a-f4e5-421e-75e6-08d6b91b0804
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB3614;
x-ms-traffictypediagnostic: MN2PR11MB3614:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(136003)(39860400002)(396003)(366004)(189003)(199004)(13464003)(2501003)(102836004)(66066001)(53936002)(25786009)(97736004)(8936002)(6436002)(7696005)(71200400001)(476003)(5660300002)(229853002)(316002)(6116002)(26005)(2906002)(76176011)(81156014)(3846002)(14454004)(99286004)(52536014)(14444005)(256004)(11346002)(7736002)(966005)(33656002)(478600001)(8676002)(86362001)(6506007)(305945005)(74316002)(105586002)(81166006)(71190400001)(106356001)(6306002)(55016002)(6246003)(486006)(53546011)(186003)(9686003)(446003)(68736007)(110136005); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3614;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Gq0+Lz1E97WA3cR8F5Bkrz3iWXz1TbXRYD15CDu91GDIMlq7lN4f9UyUBlwlWcxMBEMPH/Lktf1Sb96V91Qb0OleUjft2K4a87zM+CKTxZrFkTUJSBZVxbIgkawJuNiSqqss9uEZU3O+9O7SwGaAwaO2xpVSnXvkaFJ2JMVbeElNV7G7y6t6IqwVsl9dbftHaUhJZ0YQEFKCcT9lVrNee/4ZHcdJ7RnhVuN8V6K6/AtfK2/bdyKpz7D75OVrOQB9u9k8FTasglqiTIlVqN4GHbJ9aECjBa+4jTvqiHMMEn0WBaa/DGKx9wionCIfg1lAUkg5Mag4ZazK/PlM5jldQN+DeX/3SjN1QCnbTDTaV3jAz+KgAkwS7HXMRaRMkqtGXGUWhN8/h/n9Mty+vBaL2epUlbVGA1xdnKrmEfW9KZw=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 93a9f29a-f4e5-421e-75e6-08d6b91b0804
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 16:31:46.6887 (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: MN2PR11MB3614
Archived-At: <>
Subject: Re: [Paw] Renaming
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: predictable and available wireless <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Apr 2019 16:31:55 -0000

I agree with that, that is mostly a), but sill would love to be able to express a multihop schedule possibly across technology.
Which means that we need an abstraction at layer 3 where we can express timing offsets, things like that.
6TiSCH comes into play because from there we already have experience on multihop scheduling, even if the group itself did not work on it beyond the architecture.
What the group would describe is complex path ala DetNet but with additional properties like overhearing, HARQ, and possibly constructive interference, for which we need to extend the detNet PREOF abstraction. Depending on the radio technology it could impose a time boundary to the transmission, or even dig into link selection which may abstract a radio channel or a beam.
If you look at LPWAN, we provided generic methods like SCHC, and then there are radio specific documents that explain how this is translates on a particular radio, mostly by constraining to the subset of the generic model that is meaningful on that radio. I'd like to stick to that model of making sure that what we do is generic enough for a covered set of radios. 
I do not know if the charter will go as far as enable the group to produce c). It is not my priority but it does not seem that complicated either. If it does, I'd like to see the same for the other technologies, understanding that for the most part the scheduling is done under the cover so L3 can at bets provide hints to be defined, like a transmission deadline in absolute time.

About the name, We cannot have Deterministic in it, even hidden in the DetNet abbreviation. "Deterministic" raises too much concern/discussion on the wireless piece. We has that discussion and concluded with SPAWN. RAW came later but I find it quite good so if there was a strong support from the group, I'd see no problem to swap. 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.

At the moment the proposed charter is like this:

    The group will:

        1) Produce informational work describing deterministic wireless
           use cases, in continuation to the DetNet Use Cases document
         2) Produce informational work describing the technologies that the
            group will cover (e.g., URLLC, TSCH, EHT and LDACS) 

        3) Produce a Standards Track document to define the generic data models
           to install a SPAWN flow along a track providing packet replication, 
           elimination and ordering functions with spatial, frequency and time
           diversity in a scheduled FD/TDMA wireless network.

        4) Produce a Standards Track document to enable operations, 
           administration and maintenance (OAM) inside a SPAWN network, providing
           packet loss evaluation and automated adaptation to enable trade-offs
           between resilience and energy consumption.


Do you think we nee to change it to address better you're a, b or c question?

All the best,


> -----Original Message-----
> From: Venkatesan, Ganesh <>
> Sent: jeudi 4 avril 2019 17:11
> To: Lou Berger <>; Pascal Thubert (pthubert)
> <>;
> Subject: RE: [Paw] Renaming
> My understanding is that it is mostly (a) with some common
> management/provisioning/control that you describe in (b). DoW would
> probably be more apt for what our objectives are.
> Cheers --
> ganesh
> -----Original Message-----
> From: Paw <> On Behalf Of Lou Berger
> Sent: Thursday, April 4, 2019 7:50 AM
> To: Pascal Thubert (pthubert) <>;
> Subject: Re: [Paw] Renaming
> Hi Pascal,
>      I think it's good to ensure the name is well aligned with the objectives of
> the group/activity.  I left the BoF a little confused, is the scope of this work:
> (a) DetNet over any wireless technology using a layered (sub-)networking
> model
>      (i.e., each wireless network technology brings it's own
>       management/provisioning/control plane)
> (b) DetNet over any wireless technology using an integrated (sub-)networking
> model
>      (i.e., the objective is a single integrated management/provisioning/control
> plane
>       for DetNet and different wireless network technologies)
> (c) A control(ler) plane for 6tisch
> (d) something else
> If (a) or (b), I see no reason to not use DetNet in the name so I like DoW
> (Detnet over Wireless) or DfW (DetNet for Wireless)
> if (c) I'd include 6tisch in the name, maybe 6TC (6tisch Control)
> Lou
> On 4/4/2019 3:39 AM, Pascal Thubert (pthubert) wrote:
> >
> > Dear all:
> >
> > Before we finalize our renaming, another alternate came up, RAW, for
> > reliable available wireless.
> >
> > It's closer to PAW so it would be less of a surprise. I do not have a
> > strong opinion. Since we already advertised SPAWN maybe it's better t
> > stick to it.
> >
> > Opinions?
> >
> > Pascal
> >
> >
> --
> Paw mailing list