Re: [Paw] Towards a PAW WG

<toshio9.ito@toshiba.co.jp> Tue, 18 December 2018 07:46 UTC

Return-Path: <toshio9.ito@toshiba.co.jp>
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 BA3D01310BC for <paw@ietfa.amsl.com>; Mon, 17 Dec 2018 23:46:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.059
X-Spam-Level:
X-Spam-Status: No, score=-4.059 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=toshibaap.onmicrosoft.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 N6FZzb3JpQ9f for <paw@ietfa.amsl.com>; Mon, 17 Dec 2018 23:46:12 -0800 (PST)
Received: from mo-csw.securemx.jp (mo-csw1116.securemx.jp [210.130.202.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81265127598 for <paw@ietf.org>; Mon, 17 Dec 2018 23:46:09 -0800 (PST)
Received: by mo-csw.securemx.jp (mx-mo-csw1116) id wBI7k4j4032672; Tue, 18 Dec 2018 16:46:04 +0900
X-Iguazu-Qid: 2wGqtydX4GrVb3ZWz2
X-Iguazu-QSIG: v=2; s=0; t=1545119164; q=2wGqtydX4GrVb3ZWz2; m=O8hrjNzslvsbuIzfUAIPxLoE0M6Y2bHWZFHTpQ5/VQE=
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by relay.securemx.jp (mx-mr1111) id wBI7k4j2000336; Tue, 18 Dec 2018 16:46:04 +0900
Received: from hop101.toshiba.co.jp ([133.199.85.107]) by imx12.toshiba.co.jp with ESMTP id wBI7k3ei024565; Tue, 18 Dec 2018 16:46:03 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toshibaap.onmicrosoft.com; s=selector1-toshiba-co-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1p68LQ0b8BTU+clAG3Sax8ZBNkNWhnwZUf4iOpsqhPo=; b=2SW3UbSGbmFPP7Kzt53vKUHq6dm8QDokVlE3h9B1OF6I9oeoakl+W5wYtLwdzOsGzVdAm9RXTYhkHWHnxzqT0r7jxKpI8Tp+3mRdOBRoBtWJxW2heDpFl2rlJsPhXZ3YXPrPMHj0UQqFJzJ9pXvIG5BjLqW+8v81E5bUamvlWJw=
From: toshio9.ito@toshiba.co.jp
To: pthubert@cisco.com, paw@ietf.org
Thread-Topic: Towards a PAW WG
Thread-Index: AQHUk6+CJdcPwKK/iUaZBR0bVQ3vMqWEJUNQ
Date: Tue, 18 Dec 2018 07:46:00 +0000
X-TSB-HOP: ON
Message-ID: <OSAPR01MB3315C25D4E9E9EC3D4A71983E5BD0@OSAPR01MB3315.jpnprd01.prod.outlook.com>
References: <E50B14E5-58F7-42C7-B58E-4E3660E6AD53@cisco.com>
In-Reply-To: <E50B14E5-58F7-42C7-B58E-4E3660E6AD53@cisco.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
authentication-results: spf=none (sender IP is ) smtp.mailfrom=toshio9.ito@toshiba.co.jp;
x-originating-ip: [103.91.184.0]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; OSAPR01MB1764; 6:WiSFogQF/XxxUKxe796hlBbKpupOhx1Mop0+99cT8OmBnycB8iRr7m0eZTsOqnW89e9U+xP64xGykHSbX4OuLh5XgGiElH9r2JplZJR1+WtLzGcokHbGca+v/hnYgFPA0L3WEa7qkNufR3nZqO1Uztvf5gXrptgxxsLI83lQuMvTYRUGLo6FbSNikS8dy5t2ztjN8DtWhYSFyU7SN7/RBSS8+kUTf+luOq81QD9nh8O3ChKCCNcvOpWSkt/lddpF4AgdcaL8gFlfP0h3qMOLylbCHXDb+TFS8rtMDh3G2vybJTaGdkbKe/lFmEEoIO/PVpz+nk3MyseNptdrr/gqjIZeOixSvA+ZgODAzLKjhEmwRqF3WDc4Gb0ZFWoOmoAkiDOHZ/PujF38SrWzByS5GEg/ApDlo0rirrUF1DdcyE+Rt7R02qPIKaezwmwMjG3he5MsPqeyHwuvr9gqxZsbaQ==; 5:9aLVaBdSruFM6W5s9l3KoCm+hrIE86oWYfCl816yCAIMj2bx7wRO9YkNaQiSbBpj0dQDcREZAPEphysIUJF5TDQzI7yeWTASeom8uFXvpVEvuxrOW1GkSOJai2EpbpztqukRYCn4kUYBMnic5hXjscJjlU1ffS9fnnPrT3mnstE=; 7:CCGWj0WNHTjUR7HEcdPpgdPAvtobedBX+R5ZiOl4Ym34nGwE498RuKr0OEKMJlvRxnwtdSK6jP0GRGqCtfpfoK0FLpAXkksrAs7YNmTj07t4pj62xOhw5QkjJhKkJQSdXeL2VgN8aypoUUDBRM1udA==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 9ba44373-a731-4dd9-38f9-08d664bcdaa7
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:OSAPR01MB1764;
x-ms-traffictypediagnostic: OSAPR01MB1764:
x-microsoft-antispam-prvs: <OSAPR01MB1764326C68BF7741768D5083E5BD0@OSAPR01MB1764.jpnprd01.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(3230021)(999002)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231475)(944501520)(52105112)(3002001)(148016)(149066)(150057)(6041310)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(201708071742011)(7699051)(76991095); SRVR:OSAPR01MB1764; BCL:0; PCL:0; RULEID:; SRVR:OSAPR01MB1764;
x-forefront-prvs: 08902E536D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(376002)(39860400002)(366004)(396003)(346002)(13464003)(51874003)(199004)(189003)(6246003)(74316002)(305945005)(7736002)(71190400001)(66066001)(26005)(106356001)(71200400001)(102836004)(6506007)(53546011)(55016002)(966005)(6306002)(7696005)(9686003)(6436002)(97736004)(86362001)(53936002)(478600001)(110136005)(14454004)(8936002)(229853002)(14444005)(186003)(6116002)(74482002)(99286004)(486006)(25786009)(8676002)(2906002)(33656002)(446003)(5660300001)(316002)(76176011)(2501003)(105586002)(476003)(81166006)(256004)(81156014)(3480700005)(3846002)(11346002)(68736007)(7756004); DIR:OUT; SFP:1101; SCL:1; SRVR:OSAPR01MB1764; H:OSAPR01MB3315.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: toshiba.co.jp does not designate permitted sender hosts)
x-microsoft-antispam-message-info: xy2zvmuEULYyFGWBImc3lqR1maDLmd8mn4Jn7pn4vFbNt6EKMNPvL9ShSe8JYUrzf3gaG+gFCyZT051EAXcpmdPdzkK7/gyV9HLOz49BK9onU7RdO9UB9yh4NytFaqjCdG5zptLw+Y0FA0zKjsgHZd28WjOMDzdUbLrYdsCjWX1+1PGHB2GsTAFugmprChlCf06ggz2O0AtWYD1R9Yfrg3W3YlzPy/rdwv5q7qXTRE9ZcZK1HegwdjyYy255hNY2H3aeqdSMx/ZI9fMNhMFqMYvQV/K3VfP+KK0Mm3ZtgjKZWnz8r3uhH7QJgf6WDorR
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9ba44373-a731-4dd9-38f9-08d664bcdaa7
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2018 07:46:00.3900 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f109924e-fb71-4ba0-b2cc-65dcdf6fbe4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB1764
MSSCP.TransferMailToMossAgent: 103
X-OriginatorOrg: toshiba.co.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/s8M8__OemXLEk7UEXvcPNEp67Cw>
Subject: Re: [Paw] Towards a PAW WG
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: Tue, 18 Dec 2018 07:46:16 -0000

Hi Pascal,

I'm interested in DetNet on wireless, especially on IEEE 802.15.4
TSCH. I think some features in TSN (e.g. 802.1Qch) can be mapped
to TSCH thanks to its time-aware nature. To do that kind of
mapping, we need its data model and management interface for it.

I have a question, though. Isn't PAW covered by 6tisch WG?
draft-ietf-6tisch-architecture-19 talks about deterministic
wireless networks for industrial applications, centralized TSCH
scheduling, and packet replication. There are some expired
drafts (*1) for centralized management. I don't know what's
happened to those drafts, but I thought 6tisch WG would
eventually work on centralized networks in future. Isn't it gonna
happen?

If we are to expand our focus to include 802.11 radio, probably
6tisch WG cannot cover that.


*1: https://tools.ietf.org/html/draft-ietf-6tisch-6top-interface-04
    https://tools.ietf.org/html/draft-ietf-6tisch-coap-03



Best regards,
Toshio Ito

> -----Original Message-----
> From: Paw <paw-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
> Sent: Friday, December 14, 2018 10:19 PM
> To: paw@ietf.org
> Subject: [Paw] Towards a PAW WG
> 
> Dear all:
> 
> At the PAW bar BOF in Bangkok, we found common interests in discussing matters similar to DetNet but with
> a focus on wireless.
> 
> What’s so special with wireless? Well, in very short, scheduling brings all the benefits it does on wires,
> and more. Scheduling can enable multi channel operations, energy savings, G-MPLS forwarding operations with
> schedule-based Replication (overhearing), Elimination and Reordering.
> 
> But the methods to build a Predictable and Available Wireless network will differ from those used by
> DetNet/TSN on wires because the medium can be shared, lossy, and broadcast.
> 
> This is why we also discussed the need of a group that would specifically address the PAW problem. What
> would such a group do?
> 
> Quite simply PAW would aim at providing latency and throughput guarantees over a set of radios to be defined,
> and collaborate with the groups in charge of these radios. In more details:
> 
> - Which radios? There are 2 elephants in that room, the adult, ieee std 802.15.4 TSCH for which we have
> RFC 7554, and the young, ieee sig 802.11 RTA, for which we’d need an informational doc explaining what’s
> special and interesting about it. Also I’m hearing through the grapevine that the German DLR is developing
> a new radio that could become a standard for plane communication.
> 
> - there is a need to extend the DetNet use cases draft with a wireless twist. Cover real time gaming, in
> cars and in planes automation, conferencing, building automation, and industrial process control and factory
> automation.
> 
> - there is work that is discussed at BIER and ROLL about methods that could provide extensive time and space
> diversity using synchronized overhearing and elimination, as well as OAM techniques to optimize the use
> of the possibly extensive replication that can be needed to provide high delivery ratio with bounded latency.
> This work needs a central hosting.
> 
> - 6TiSCH provides IP best effort over a PAW-capable radio, but did not work on the deterministic flows.
> We are missing the data model to control the GMPLS forwarding over complex Tracks that is described in the
> 6TiSCH architecture. PAW would be the natural place to do that.
> 
> - ... <anything I missed?>
> 
> All and all, there is quite a bit of work ahead. But then, we need to show that we can build a critical
> mass of people to form a WG. This is where this list comes into play.
> 
> So please respond, indicate what radio we could work on, what network layer problem we need to solve, what
> amount of energy you are willing to make this happen. Don’t be shy!!
> 
> Many thanks in advance...
> 
> Pascal
> 
> --
> Paw mailing list
> Paw@ietf.org
> https://www.ietf.org/mailman/listinfo/paw