Re: [Raw] Skeleton for a technologies document

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 21 May 2019 14:56 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: raw@ietfa.amsl.com
Delivered-To: raw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948BC120153 for <raw@ietfa.amsl.com>; Tue, 21 May 2019 07:56:29 -0700 (PDT)
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, 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, 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=MWGw3BkH; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Y+xr6Gf1
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 obgRGzTIT8Ns for <raw@ietfa.amsl.com>; Tue, 21 May 2019 07:56:27 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07A3E120120 for <raw@ietf.org>; Tue, 21 May 2019 07:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37166; q=dns/txt; s=iport; t=1558450587; x=1559660187; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1m4X0tS0slvT8LhIwKXVXpEHjrObuOClPMoz2YKtdUo=; b=MWGw3BkHMlSKlohWKAY2x/6yvsV3crRTRZtuyWZGZcirp+2voyoPDlun CD0ffiO655NgDFGMEaDXS4AEvupV8i1huDJmsHcLLFEhMPDEmZPPiWEcz D339rLLVAqhzg8suUzARjr+DOWcxjsiDGDQ0tvTJJCA99kogNBBzU05HJ I=;
IronPort-PHdr: 9a23:K5jbfRMWu3GThV3BzMEl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjjMP73ZSEgAOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CBAACsEORc/4QNJK1lDg4BAQEEAQEHBAEBgVIGAQELAYEOL1ADaVUgBAsVE4QTg0cDjnaCV4MKlB2BLhSBEANUCQEBAQwBARgBBwkEAgEBhEACF4IPIzUIDgEDAQEEAQECAQRtHAyFSgEBAQQBARARChMBASwLAQ8CAQgRBAEBIQcDAgICJQsUCQgBAQQBDQUIGoJKN4EdTQMdAQIMm3ECgTWIX3GBL4J5AQEFgQcBKwEDAg5Bgn0Ygg8JgR0XAYRmg02DHReBQD+BEUaBTn4+ghkBOwwBAQEBAQEWgQ86FRYJCIJMFxuCBCKLJhKCQoReiBqNNQkCgg2GLoZAhi2CHmeFdI0zizuBG4ZyjlYCBAIEBQIOAQEFgT0TATaBV3AVO4JsCQmBWSSDb2qEKoUEBAE2cgEBE4EUjggBAQ
X-IronPort-AV: E=Sophos;i="5.60,495,1549929600"; d="scan'208,217";a="565648262"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 May 2019 14:56:24 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x4LEuOVN017364 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 21 May 2019 14:56:24 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 09:56:24 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 10:56:23 -0400
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 21 May 2019 10:56:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1m4X0tS0slvT8LhIwKXVXpEHjrObuOClPMoz2YKtdUo=; b=Y+xr6Gf12FEUSMjFJcQr498Ww9xZyAJJW09YOv3oJRNcT+ugSAf+ZZ1GErvP52VRE0SUisNUHLmZZg7zNm48WT/MNMDl3w1ghcIh6DooeoLN38j06lHUL6c+RP/s9aYNqwDhZGfPJksRZNjroOUteNKRlxR4Y+iLJR66mCTB5yo=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3582.namprd11.prod.outlook.com (20.178.251.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.17; Tue, 21 May 2019 14:56:17 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::7cc2:b440:8820:f0fc]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::7cc2:b440:8820:f0fc%7]) with mapi id 15.20.1900.020; Tue, 21 May 2019 14:56:17 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Xavi Vilajosana Guillen <xvilajosana@uoc.edu>, Charlie Perkins <charles.perkins@earthlink.net>, Edgar Ramos <edgar.ramos@ericsson.com>, Bikramjit Singh B <bikramjit.b.singh@ericsson.com>, Muhammad Shahwaiz Afaqui <mafaqui@uoc.edu>, "Cavalcanti, Dave" <dave.cavalcanti@intel.com>, "Jerome Henry (jerhenry)" <jerhenry@cisco.com>, Hesham ElBakoury <Hesham.ElBakoury@huawei.com>, "Georgios Z. Papadopoulos" <georgios.papadopoulos@imt-atlantique.fr>, "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
CC: "raw@ietf.org" <raw@ietf.org>
Thread-Topic: Skeleton for a technologies document
Thread-Index: AdUO/uE4YU5jzMYXR3aTrtLej4DsLQA5Kk0w
Date: Tue, 21 May 2019 14:55:49 +0000
Deferred-Delivery: Tue, 21 May 2019 14:55:16 +0000
Message-ID: <MN2PR11MB356566817A3BB8F78275A4ECD8070@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB35650BFEAC9523EC7CEB9697D8060@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB35650BFEAC9523EC7CEB9697D8060@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: d6c3d27e-46cb-4ad4-c8eb-08d6ddfc7a52
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR11MB3582;
x-ms-traffictypediagnostic: MN2PR11MB3582:
x-ms-exchange-purlcount: 15
x-microsoft-antispam-prvs: <MN2PR11MB3582A248C0AE73474FC6F3B5D8070@MN2PR11MB3582.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3826;
x-forefront-prvs: 0044C17179
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(396003)(39860400002)(136003)(366004)(199004)(189003)(6306002)(54896002)(236005)(2171002)(46003)(6246003)(7416002)(53386004)(4326008)(66574012)(55016002)(186003)(74316002)(2906002)(9686003)(5660300002)(606006)(486006)(14454004)(11346002)(446003)(53936002)(790700001)(6116002)(476003)(7696005)(229853002)(99286004)(110136005)(52536014)(6666004)(66556008)(66476007)(66446008)(71200400001)(76116006)(64756008)(68736007)(71190400001)(66946007)(73956011)(7736002)(6436002)(25786009)(86362001)(102836004)(478600001)(53546011)(81156014)(33656002)(6506007)(256004)(8676002)(733005)(966005)(76176011)(8936002)(81166006)(316002)(921003)(1121003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3582; 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: eQOEk9fs6r+K26jSk3q3ivgEpPGrcF08x5wrsKpRWZeeg8bjHFLvtGbkmgTF7LIOBijf7uA9YhoketqFnIM4LlM2K3+RFP0zl3fxJdtfO7MlSG/XRy827/EH/RZwAlJtRGVapm6K3G8brbyq/YnIwuQlZlTNrxLpTyp6kSRT2jyRRi80cf8jfBIWQh2keiXFYpwCsQWLoeER+xq+5B3nlJ3uwPh2Q44ycEKjQFpqEWdBBl6utwly75M4vFzi5zkkGrACUvnBuLZfVT8jqOFHVYEUIfKbO6faKcFvcMk7pffIdAqqjgaXiUAsPoSbUIgBpofVSTvnoAdkNfpPsU36PAXjMl12TnXXmmoYZc/u9O5fMaPe+Iuz/9zlUxf7MgamuJcb/tXZZjAwUzxXZ1PtEKZEG6nKsyB6MgyEWKsVpkU=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB356566817A3BB8F78275A4ECD8070MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d6c3d27e-46cb-4ad4-c8eb-08d6ddfc7a52
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2019 14:56:17.2697 (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: MN2PR11MB3582
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.23, xch-aln-013.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/b8GHUg1-mgjyQo2bWWMm7FFM8uo>
X-Mailman-Approved-At: Tue, 21 May 2019 10:12:02 -0700
Subject: Re: [Raw] Skeleton for a technologies document
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: reliable and available wireless <raw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/raw>, <mailto:raw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/raw/>
List-Post: <mailto:raw@ietf.org>
List-Help: <mailto:raw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/raw>, <mailto:raw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2019 14:56:30 -0000

Dear all:

I created a repo https://github.com/pthubert/raw-techs
Also published a skeleton as 00:

URL:            https://www.ietf.org/internet-drafts/draft-thubert-raw-technologies-00.txt

Status:         https://datatracker.ietf.org/doc/draft-thubert-raw-technologies/

Htmlized:       https://tools.ietf.org/html/draft-thubert-raw-technologies-00

Htmlized:       https://datatracker.ietf.org/doc/html/draft-thubert-raw-technologies

Now we need an editor and contributors for all techs

From the previous answers I would see:

Tech                    Editor                 Contributors
-------------------------------------------------------------
EHT                     Dave                   Jerome, Diego
TSCH                   Xavi                    Georgios, Charlie, Muhammad
URLLC                 Edgard                Bikramjit, Hesham

I can organize calls between authors on demand. The plan could be that each editor owns a file that is his section and I do merge before publishing.
I created several files in the repo for that purpose. But I’m open to other models as you prefer.

All the best,

Pascal

From: Raw <raw-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: lundi 20 mai 2019 13:28
To: Xavi Vilajosana Guillen <xvilajosana@uoc.edu>; Charlie Perkins <charles.perkins@earthlink.net>; Edgar Ramos <edgar.ramos@ericsson.com>; Bikramjit Singh B <bikramjit.b.singh@ericsson.com>
Cc: raw@ietf.org; Muhammad Shahwaiz Afaqui <mafaqui@uoc.edu>
Subject: [Raw] Skeleton for a technologies document

Great!

We need to agree on a skeleton that is generic for all technologies. Then the editor for each technology needs to produce his piece so I can wrap it all together. Each editor would be responsible for his technology and get the helps he finds relevant.
For now I see that we can achieve TSCH and Wi-Fi, but we are short on URLLC, cc’ing Edgard and Bikramjit for help.
Let me suggest the below, please suggest additions:


   2.  RAW-capable Technologies  . . . . . . . . . . . . . . . . . . . . .   3

     2.X.1.  Tech X . . . . . . . . . . . . . . . . . . . . . . . . .   4


       2.X.1.  Provenance and Documents  . . . . . . . . . . . . . .   4

              - Which SDO, position wrt Open standards
             - Existing IP over foo
              - TSN-like activities, past and present (introduce the likes of as OFDMA, URLLC and EHT)
              - DetNet-like arching art (introduce the likes of ISA100.11a or WiHART)

       2.X.2. General Characteristics . . . . . . . . . . . . . . . . . . .   4
              - bandwidth, beam forming
              - expected capabilities for safety and automation, e.g., loops per second
              - caveats, e.g., latency in the backhaul or interference
              - programming capabilities, is there a model for a flow, etc.

       2.X.3. Applicability to deterministic flows . . . . . . . . . . . . . . . . . . .   4
              - time synchronization
              - scheduling capabilities, discuss such things as Resource Units, time slots or resource blocks. Can we reserve periodic resources vs. ask each time, what precision can we get in latency control.
              - diversity scenarios, what’s available,
              - gap analysis, e.g. discuss multihop, or what’s missing how to do PAREO features.


All the best,

Pascal

From: Xavi Vilajosana Guillen <xvilajosana@uoc.edu<mailto:xvilajosana@uoc.edu>>
Sent: lundi 20 mai 2019 11:59
To: Charlie Perkins <charles.perkins@earthlink.net<mailto:charles.perkins@earthlink.net>>
Cc: Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>; raw@ietf.org<mailto:raw@ietf.org>; Muhammad Shahwaiz Afaqui <mafaqui@uoc.edu<mailto:mafaqui@uoc.edu>>
Subject: Re: [Raw] technologies document

Pascal, all,

maybe we can also help with 6TiSCH and 802.11ax and upcoming 802.11be

please let us know how to proceed.

X

Missatge de Charlie Perkins <charles.perkins@earthlink.net<mailto:charles.perkins@earthlink.net>> del dia ds., 18 de maig 2019 a les 1:00:

Hello folks,

I can help with 802.15.4, although I am weak on numerous PHY layer details.

Regards,
Charlie P.


On 5/17/2019 3:44 PM, Grossman, Ethan A. wrote:
I can help with editing but I can’t commit to core technology text.
Ethan.

From: Raw <raw-bounces@ietf.org><mailto:raw-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: Friday, May 17, 2019 2:30 AM
To: raw@ietf.org<mailto:raw@ietf.org>
Subject: [Raw] technologies document

Dear all

We are missing activity to justify a BoF in Montreal... A good starting point – and a low hanging fruit - for us is to kick off the technology draft. Something inspired by https://tools.ietf.org/html/rfc8376<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc8376&d=DwMFAg&c=lI8Zb6TzM3d1tX4iEu7bpg&r=ZcHC6wX_gDwPDcfMaFNZiQ&m=k0kmef03JJi_WmayGA-A3wF562FPiIH0fO_KZQ34fAM&s=Eg2fCle_1uXJ-04aOl7PPbH9L5MBZcEDrAXg_R9Xbmw&e=> and possibly taking information off other docs such as https://tools.ietf.org/html/rfc7554<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7554&d=DwMFAg&c=lI8Zb6TzM3d1tX4iEu7bpg&r=ZcHC6wX_gDwPDcfMaFNZiQ&m=k0kmef03JJi_WmayGA-A3wF562FPiIH0fO_KZQ34fAM&s=XcHvOngTavHuYitUzvMkBjbhirpoGG_ZidH_P51C_NA&e=>.

The idea of that draft would be to describe the characteristics of the technologies that RAW would deal with, in particular 802...11 EHT, 3GPP URLLC and 802.15.4 TSCH.

On top of the usual description, we’d need information such as the capability to schedule resources and typical rates, typically for a constant DetNet flow that can be expressed in frame size and period. The draft should also cover applicability to Use Uses such as presented in the use cases draft (https://tools.ietf.org/html/draft-bernardos-spawn-use-cases-00)

I can provide  a skeleton for the document, but need authors to commit to the work.

Who’s in?

Pascal

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


--
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]
­