Re: [Paw] tentative PAW charter

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 06 February 2019 10:58 UTC

Return-Path: <pthubert@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 EF7711295D8 for <paw@ietfa.amsl.com>; Wed, 6 Feb 2019 02:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.643
X-Spam-Level:
X-Spam-Status: No, score=-14.643 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=E6BYieeL; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=nW1T8m0e
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 yAqbsoZiGfQj for <paw@ietfa.amsl.com>; Wed, 6 Feb 2019 02:58:34 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1CC612D4EB for <paw@ietf.org>; Wed, 6 Feb 2019 02:58:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19731; q=dns/txt; s=iport; t=1549450713; x=1550660313; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=h0QPulVAmzqGV8LXrwntE4/UWZufe696SSqZshF7hZs=; b=E6BYieeLL4d1UCOx8EaNMXKLrGe/yB3XVO6VBIWhLc46rFr52xv7bHSB pZCBPJcG7ZFby7JSvWlVzfodB16ceXgBYqN8XmduBBelktcu88RkkFNZD ZyWDtTN5REyGflNQ15RoIhzEELijxqMAer27Op072CasWkdqMgFa6G+tC 4=;
X-Files: charter.txt : 3872
IronPort-PHdr: 9a23:8Vfr2hTEnmiFFKxrOUwvqj2lNtpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOjQmHNlIWUV513q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BZAACVvVpc/49dJa1lHAEBAQQBAQcEAQGBUwUBAQsBgTAlKwNndAQLFRIKh0ADj3BKgg18jjKIYRSBEANUCwEBGA0HhEACgxciNgcNAQMBAQIBAQJtHAyFSgEBAQQBAT4BASwCCgsEAgEIEQEDAQEoBwIlCxQDBggCBAESCAYNgwiBaQMVAQIMoVsCihSCIIJ4AQEFgTABAwODXRiCBAcDBYxDF4FAP4ERRoFOSTWDHgEBAYEoOhWDI4ImiV0kBxEJDYVqZ4YjiiWBQQkChESCBG2FRYVfgWyFRYd0gyeJXFCBDIQmjA8CBAIEBQINAQEFgU0FLIFWcBU7gmyCHINuhRSFP3IBAYEmjDMBgR4BAQ
X-IronPort-AV: E=Sophos;i="5.58,339,1544486400"; d="txt'?scan'208";a="428676682"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Feb 2019 10:58:32 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x16AwW8l005953 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 6 Feb 2019 10:58:32 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 6 Feb 2019 04:58:31 -0600
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 6 Feb 2019 05:58:30 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 6 Feb 2019 04:58:29 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7tfVwd7xbnJhAQ6r8NbpYYTDhBC2kdPDrjeivrsE9G0=; b=nW1T8m0egVGniFnxLgDXOsBPe6cuVTmxR5v+HgaLAk1WLyqnoFBY2akNtoyim7HOQKsrAORTzOA/5c7RMbZY7O8iZdo/QFOW0/KkekioHJiqcASoK48lUhZW894zEjl25HfE6/haeNPpKIJx99Q9LP/LqpYs2d3yUl6yMlCpVGE=
Received: from SN6PR11MB3471.namprd11.prod.outlook.com (52.135.112.221) by SN6PR11MB3485.namprd11.prod.outlook.com (52.135.112.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1601.17; Wed, 6 Feb 2019 10:58:29 +0000
Received: from SN6PR11MB3471.namprd11.prod.outlook.com ([fe80::1c9f:935:667b:8957]) by SN6PR11MB3471.namprd11.prod.outlook.com ([fe80::1c9f:935:667b:8957%3]) with mapi id 15.20.1580.019; Wed, 6 Feb 2019 10:58:29 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "Grossman, Ethan A." <eagros@dolby.com>, "Cavalcanti, Dave" <dave.cavalcanti@intel.com>, "paw@ietf.org" <paw@ietf.org>
Thread-Topic: tentative PAW charter
Thread-Index: AdS5cp1HVs28gzanRP2Hl9funa/jvAA2xSygAIMZnAAACEfp8AAYNWggABI6JeAAGA9j8AAgGbQQAAFERSA=
Date: Wed, 06 Feb 2019 10:58:10 +0000
Deferred-Delivery: Wed, 6 Feb 2019 10:58:06 +0000
Message-ID: <SN6PR11MB3471E78145089E0B1FE245F9D86F0@SN6PR11MB3471.namprd11.prod.outlook.com>
References: <425c1074d34c42d595902528d1a55858@XCH-RCD-001.cisco.com> <167E9B9F5274D7459E354580CC4EFD7A41D97F60@ORSMSX101.amr.corp.intel.com> <97743e23ea814f22b5e3d188117d5dff@XCH-RCD-001.cisco.com> <bd33e96ad56b443bbfcdde26f327cab9@XCH-RCD-001.cisco.com> <BYAPR06MB4325D84477A3A6013D73BDFBC46D0@BYAPR06MB4325.namprd06.prod.outlook.com> <BYAPR11MB34644CFC81E3B45C36F8D731D86E0@BYAPR11MB3464.namprd11.prod.outlook.com> <BYAPR06MB432546EF0C0E9D9ECC2F2884C46E0@BYAPR06MB4325.namprd06.prod.outlook.com> <SN6PR11MB347197AED7B62C8C74864AD5D86F0@SN6PR11MB3471.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB347197AED7B62C8C74864AD5D86F0@SN6PR11MB3471.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [173.38.220.34]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN6PR11MB3485; 6:xfsXmDojrubnkRfvBFCxdkZzjidm5Qz6y/YVUrOjc5ovaeCS58y3KftqplCJS4tQwgdGA4KhmltHHrFJij1NXkVI2j26p40HXtJS/tY/YoxmoiN2I7EqR3bsyXolUt7bVLwsZgQ0W00/Zcujc/F4RZKVVKaNRQTeOZcjyX9DcWgJELHRnhpGnL5UlyoPF4D5aJPw4WSP+9dbfcFWbErE6D7kK+ISAMD8IdISQ8RN72/QlbEIpvXP49dYnqAuQzDs4AZBNe4XvM5KWwC91PnJZFY1k13nNRY4jt3D/JbehrlAHzK8h5nzBBu+Fhm3sd/1RfA282lPPyUgBrDOLJU2HouZxC3TH3/Iu5+Lstu/pzT3gp3OL+1ZBJeAtxztgSNMX7Kc3dXpw3u5cQ5//LD9kLaw3xCF0dP2h+uo2jj3/q/ly0GjVrn49jXe3tTbQsiN7DfCbQoD9sFJEcALzR6SSA==; 5:nPVn/myd6oZ+ftYcD79Pj3jo8vGdBSxQGJI3ZmBZF5OvaLLNHsj71QHWBhcBo7wjAmJVUSES4HUL/Qs3QhFVbK0V6exiOfrkPzRi1jQ0qz72en6JbGQ/W/29OCfJwQ9cJerA6+BE/i2Hm0abynMPWdH8MJs3kD/maqiqpCHruk6G2GcnjuxHFvu+ggx4E+9rcIfzn90EiBWdL6wog5Ne3w==; 7:Safewj4JRLnC6b3p8w+klgNkkLRti5ksuAeu2XMBWucJPSQt+Ar+45R5+5lVtbDmn5Ef3aJNVnu5GpQJk7BYcxNyE4mJFau+a6nvFK/1fhFjYqj0hr4sBZ5Zm7uhgTAoyKep7XT8CSnSkkZ5mueW8Q==
x-ms-office365-filtering-correlation-id: 22bb8a12-6c8b-495a-b9b6-08d68c2206cb
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(2017052603328)(7153060)(49563074)(7193020); SRVR:SN6PR11MB3485;
x-ms-traffictypediagnostic: SN6PR11MB3485:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <SN6PR11MB348584FB99F10625EEED6C9AD86F0@SN6PR11MB3485.namprd11.prod.outlook.com>
x-forefront-prvs: 0940A19703
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39860400002)(396003)(376002)(366004)(136003)(85664002)(13464003)(199004)(189003)(486006)(446003)(476003)(66066001)(68736007)(2940100002)(11346002)(74316002)(86362001)(30864003)(71190400001)(110136005)(229853002)(71200400001)(478600001)(26005)(7116003)(93886005)(966005)(316002)(14454004)(6246003)(66574012)(6506007)(97736004)(53546011)(2501003)(53936002)(7696005)(76176011)(3846002)(186003)(6116002)(102836004)(2906002)(99286004)(6666004)(3480700005)(33656002)(14444005)(5024004)(55016002)(81156014)(99936001)(8676002)(256004)(25786009)(9686003)(6306002)(105586002)(305945005)(106356001)(93156006)(7736002)(81166006)(8936002)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB3485; H:SN6PR11MB3471.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: kLaJifgVqGxTZ0XXmZL8WjpWNVPbW0oHC+d/w00kIkkeOjO6gPfeEaeuR1rRPTETdA04gkLExj+2GYop0J7RzbVfQEcHiIJlXXaKuei/AHHT3B9+34J3PfoEvwl4eBm1HxdWCHDTPXONaPWBKbPxfrtysHMXJBQnuKSZLQlqWxz6aZNv4V9SeS58APhuyCNRPl17fvDhO6cHtvKrKaebkyO0IuM/d0jzA4QD9CIWZYMXjS2jB0w6o1lFm+OwBlU75g0hyKZjkARu5v3q40p79NmLUo6Ld7/WlmY1KFlzjEOWPR0im7xBbd8u4vuPQYzUh7coSY/rrq1Ub6WRKEVjIyX4Mq8JEJVcNy4a0ww2RkRzWjI4l1MteNdLLGufLohQUaVPYmQ6uSeNG6t7kNP0ikzjahpMg8NZGQGHIWJBYrQ=
Content-Type: multipart/mixed; boundary="_002_SN6PR11MB3471E78145089E0B1FE245F9D86F0SN6PR11MB3471namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 22bb8a12-6c8b-495a-b9b6-08d68c2206cb
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2019 10:58:28.8794 (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: SN6PR11MB3485
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/DFtfBY5Qg4g61ypqRXceBKpP6Cg>
Subject: Re: [Paw] tentative PAW charter
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: Wed, 06 Feb 2019 10:58:49 -0000

Slight update ... 

All the best,

Pascal

-----Original Message-----
From: Paw <paw-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: mercredi 6 février 2019 11:49
To: Grossman, Ethan A. <eagros@dolby.com>; Cavalcanti, Dave <dave.cavalcanti@intel.com>; paw@ietf.org
Subject: Re: [Paw] tentative PAW charter

Hello Ethan:

My understanding is that in the charter, which is a contract between the WG and the IESG, we cannot be vague with text like " and other wireless protocol developments, " because we will be asked precisely what they are. 
At the IETF and for all I know, only DetNet and 6TiSCH care about determinism, so I guess we'd better leave it at that.

Similarly, the sentence "
	Thus we propose to pursue deterministic wireless in PAW, an IETF Working
	Group, coordinated with (but not part of) the DetNet Working Group.
" is needed for BoF slides and Ad discussion, but then again is not really good for a charter.

I remixed a bit and there we are, please find attached a proposed revision.

All the best,

Pascal

-----Original Message-----
From: Paw <paw-bounces@ietf.org> On Behalf Of Grossman, Ethan A.
Sent: mardi 5 février 2019 20:03
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Cavalcanti, Dave <dave.cavalcanti@intel.com>; paw@ietf.org
Subject: Re: [Paw] tentative PAW charter

OK, here's what I put together. I also attempted to clarify some of the other language, without intending to change the import of it. 
Ethan.

-----Original Message-----
From: Pascal Thubert (pthubert) <pthubert@cisco.com> 
Sent: Monday, February 04, 2019 11:36 PM
To: Grossman, Ethan A. <eagros@dolby.com>; Cavalcanti, Dave <dave.cavalcanti@intel.com>; paw@ietf.org
Subject: RE: tentative PAW charter

I agree with both Ethan. Could you propose text?
For your convenience I attached a txt file.

All the best,

Pascal

-----Original Message-----
From: Grossman, Ethan A. <eagros@dolby.com> 
Sent: mardi 5 février 2019 00:01
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Cavalcanti, Dave <dave.cavalcanti@intel.com>; paw@ietf.org
Subject: RE: tentative PAW charter

Hi Pascal,
I have a couple of general comments, and if we agree in principle then if needed I could provide some specific text. 
1) Since this is an IETF project I think the use cases you mention in the opening paragraph should be IP use cases (as opposed to TSN use cases like automotive) - I would stick with a subset of the DetNet Use Cases (not that I'm biased). 
2) The phrase about "implement the scheduled aspect of the 6TiSCH Architecture" seems too specific to 6TiSCH, given the clarification below that we would be considering scheduled wireless in general. I mean, so as not to give the impression that we are just serving that specific technology (that you happen to be heavily involved in). 

Ethan.

-----Original Message-----
From: Paw <paw-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: Monday, February 4, 2019 3:21 AM
To: Cavalcanti, Dave <dave.cavalcanti@intel.com>; paw@ietf.org
Subject: Re: [Paw] tentative PAW charter

Dear all:

Please find below the reworded text. Comments welcome!

	Deterministic Networking is getting traction in multiple industries 
	(manufacturing, vehicle automation, professional A/V, gaming) with recent
	developments in wired technologies (IEEE 802.1 TSN, IETF DetNet), enabling 
	the promises of the IT/OT convergence. 
	
	Deterministic Networking in the IP world is an attempt to eliminate packet 
	loss for a committed bandwidth while ensuring a worst case end-to-end 
	latency, regardless of the network conditions and across technologies. 
	
	IP networks become more deterministic when the effects of statistical
	multiplexing (jitter and collision loss) are eliminated. This requires a 
	tight control of the physical resources to maintain the amount of traffic
	within the physical capabilities of the underlying technology, e.g., by the 
	use of time-shared resources (bandwidth and buffers) per circuit, and/or by
	shaping and/or scheduling the packets at every hop.

	Wireless operates on a shared medium, and transmissions cannot be fully
	deterministic due to uncontrolled interferences, including the 
	self-induced multipath fading. But scheduling enables to alleviate those 
	effects	by leveraging diversity in the spatial, time and frequency domains, 
	and provide a more Predictable and Available Wireless (PAW) service.
	
	The wireless and wired media are fundamentally different at the physical 
	level, and while the generic Problem Statement for DetNet applies to the 
	wireless medium as well as to wires, the methods to achieve PAW necessarily
	differ from those used to support Time-Sensitive Networking over wires.  
	
	The development of PAW technologies was so far lagging behind that of wires
	both at the IEEE and the IETF. But recent efforts at the IEEE and 3GPP 
	indicate that wireless is finally catching up at the lower layer and that 
	time has come for the IETF to extend DetNet to wireless and implement the 
	scheduled aspect of the 6TiSCH Architecture.
	
	PAW will centralize efforts that inherit from DetNet and 6TiSCH but focus 
	on scheduled wireless. The Working Group will leverage cross-participation
	with the associated set of stakeholders to ensure that the work taking place
	corresponds to real demands and that the proposed solutions are indeed 
	applicable. It will focus on enabling PAW connectivity over the following
	selection of deterministic wireless technologies: IEEE Std. 802.15.4 
	timeslotted channel hopping (TSCH), 3GPP 5G ultra-reliable low latency 
	communications (URLLC), IEEE 802.11 extreme high throughput (EHT) and the 
	L-band Digital Aeronautical Communications System (LDACS).

    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 (5G, TSCH, RTA and LDACS) 

        3) Produce a Standards Track document to define the generic data models
           to install a PAW 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 some operations, 
           administration and maintenance (OAM) inside a PAW network, providing
           packet loss evaluation and automated adaptation to enable a trade off
           between resilience and energy spending.




What do you think?

Pascal

-----Original Message-----
From: Pascal Thubert (pthubert) 
Sent: lundi 4 février 2019 08:23
To: 'Cavalcanti, Dave' <dave.cavalcanti@intel.com>; paw@ietf.org
Subject: RE: tentative PAW charter

Many thanks Dave,

I'll update the tentative charter accordingly (s/RTA/EHT).

All the best,

Pascal

-----Original Message-----
From: Cavalcanti, Dave <dave.cavalcanti@intel.com> 
Sent: vendredi 1 février 2019 17:59
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; paw@ietf.org
Subject: RE: tentative PAW charter

Hi Pascal and All,

Thanks for sharing the draft charter. Here is an update on the related activities in the IEEE 802.11 working group:

The RTA TIG is finalizing a report that includes several time-sensitive use cases, requirements and potential solutions/areas for enhancements in 802.11 to better support RTA/TSN applications. Here is the link to the draft report:
https://mentor.ieee.org/802.11/dcn/18/11-18-2009-04-0rta-rta-report-draft.docx

The group arrived to a consensus in the January meeting that the work to be done in support of RTA should be done in the upcoming 802.11 EHT group (currently EHT is a Study Group and it is expected to be a new TG in May). The RTA TIG will finalize its report and conclude its activities in the next meeting (March), and the work will continue in EHT. 

Given this status, we could leverage the use cases/requirements defined by the RTA TIG, but we should avoid pointing to 802.11 RTA as a new solution, this may give the wrong impression that there will be a new 802.11 RTA specific amendment. Going forward, we should refer to 802.11 EHT as the group that will develop new MAC/PHY capabilities and address the RTA/TSN requirements.

Thanks
Dave



-----Original Message-----
From: Paw [mailto:paw-bounces@ietf.org] On Behalf Of Pascal Thubert (pthubert)
Sent: Thursday, January 31, 2019 6:40 AM
To: paw@ietf.org
Subject: [Paw] tentative PAW charter

Dear all:

As you know, we asked for a non-WG forming BoF at IETF 103 in Prague. If we are successful there, the aim is for a WG-forming BoF in Montreal. 
This really means that Prague is our chance to prepare for the real deal in Montreal, where we will have to show realistic goals and a critical mass of people to achieve them.
The core of the Montreal meeting will be the charter discussion. We'll present the technologies we support, and the documents we want to produce.

The work on the charter must start now, so we can narrow it down at IEF 103 and present it mostly complete at IETF 104. 
Based on early discussions at the Bar-BoF in Bangkok, please find below a for shot at the charter. Comments welcome!

Early PAW charter v0.1
-------------------------------
	
	Deterministic IP Networks are getting traction in multiple industries 
	(manufacturing, vehicle automation, professional A/V, gaming) with new
	developments in wired technologies (IEEE 802.1 TSN, IETF DetNet), enabling 
	the promises of the IT/OT convergence. 
	
	A perfect Deterministic IP Network would ensure that a bounded throughput
	of IP packets reaches its destination within a guaranteed time. In an
	imperfect world, Deterministic Networking is an attempt to eliminate packet
	loss for a committed bandwidth while ensuring a worst case end-to-end 
	latency, regardless of the network conditions and across technologies. 
 
    	Networks become more deterministic when the effects of statistical
	multiplexing are eliminated. This can be achieved by maintaining the
	amount of traffic within the physical capabilities of the technology,
	e.g., by the use of time-shared resources (bandwidth and buffers) per
	circuit, and/or by shaping and/or scheduling the packets at every hop.

    	Other types of physical-domain issue, e.g., a radio interference, a
	broken interface adapter, or an unplugged physical wire, can also be a
	source of data loss. When such breakage occurs, multiple packets are lost
	in a row before a flow is rerouted or the system recovers. Whereas random 
	packet loss can be solved by packet redundancy techniques (FEC, ARQ) these
	systemic issues a require higher-level redundancy at the path level.

	People might argue that wireless cannot be fully "deterministic" due to 
	uncontrolled interferences, including the self-induced multipath fading. 
	At least it is possible to provide a more Predictable and Available
	Wireless service by scheduling transmissions. Scheduling enables to create 
	diversity in the network in the spatial (multipath), time (scheduling) and
	frequency (hopping) domains, and get around all forms of interferences.
	
	The development of deterministic wireless technologies was so far lagging 
	behind that of wires both at the IEEE and the IETF. But recent advances
	(3GPP 5G, IEEE 802.11 ART, IEEE 802.15.4 TSCH, as well as proprietary and 
	military approaches) indicate that wireless is finally catching up at the
	lower layer and that time has come for the IETF to implement the 6TiSCH 
	Architecture and extend DetNet to wireless interfaces.
      
    	The Working Group will leverage cross-participation with the associated 
	set of stakeholders to ensure that the work taking place corresponds to 
	real demands and that the proposed solutions are indeed applicable. It 
	will focus on enabling PAW connectivity over the following selection of 
	deterministic wireless technologies: 3GPP 5G, IEEE Real Time Application 
	(RTA) 802.11 TIG, IEEE Std. 802.15.4 TSCH and possibly the L-band Digital
	Aeronautical Communications System (LDACS).

    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 (5G, TSCH, RTA and LDACS) 

        3) Produce a Standards Track document to define the generic data models
           to install a PAW 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 some operations, 
           administration and maintenance (OAM) inside a PAW network, providing
           packet loss evaluation and automated adaptation to enable a trade off
           between resilience and energy spending.


-----------------------------

Cheers,

Pascal


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

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