Re: [Paw] Towards a PAW WG

<toshio9.ito@toshiba.co.jp> Tue, 18 December 2018 08:58 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 28C1C1310E2 for <paw@ietfa.amsl.com>; Tue, 18 Dec 2018 00:58:18 -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 jcIJxeX4-il1 for <paw@ietfa.amsl.com>; Tue, 18 Dec 2018 00:58:14 -0800 (PST)
Received: from mo-csw.securemx.jp (mo-csw1516.securemx.jp [210.130.202.155]) (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 2CF371310B8 for <paw@ietf.org>; Tue, 18 Dec 2018 00:58:14 -0800 (PST)
Received: by mo-csw.securemx.jp (mx-mo-csw1516) id wBI8w9Ct011304; Tue, 18 Dec 2018 17:58:09 +0900
X-Iguazu-Qid: 34tIXmtiaDzcyw7zD1
X-Iguazu-QSIG: v=2; s=0; t=1545123489; q=34tIXmtiaDzcyw7zD1; m=D+inHzMQBFu5LTQfP+JmNcprrvZHxLVAXeDReac6Hmo=
Received: from imx2.toshiba.co.jp (imx2.toshiba.co.jp [106.186.93.51]) by relay.securemx.jp (mx-mr1512) id wBI8w88s032890; Tue, 18 Dec 2018 17:58:09 +0900
Received: from hop001.toshiba.co.jp ([133.199.164.63]) by imx2.toshiba.co.jp with ESMTP id wBI8w897025510; Tue, 18 Dec 2018 17:58:08 +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=ChDyNhkwTfCSAqKn36ydFX2eqn0q4H173jlcMK2MOEo=; b=QLbQ4AIbcEhYqUGO1ELaoISmpor9uITmPQ0mW7lOGtmac7hmBjANyAlFNv7nhuDlx/9mlOH7SIfl0vXSAfQiSfZDMyTxVRvjjD3VOV/aoaSIPUp+w2JPbV6kIYLmZzEGmRkmtuueAcQfQuMJaL8fQ712zEWRu8tAJUBLM59o/Ik=
From: toshio9.ito@toshiba.co.jp
To: pthubert@cisco.com, paw@ietf.org
Thread-Topic: Towards a PAW WG
Thread-Index: AQHUk6+CJdcPwKK/iUaZBR0bVQ3vMqWEJUNQ////9/CAABIKYA==
Date: Tue, 18 Dec 2018 08:58:05 +0000
X-TSB-HOP: ON
Message-ID: <OSAPR01MB3315A9AD013F94EC4938D8FEE5BD0@OSAPR01MB3315.jpnprd01.prod.outlook.com>
References: <E50B14E5-58F7-42C7-B58E-4E3660E6AD53@cisco.com> <OSAPR01MB3315C25D4E9E9EC3D4A71983E5BD0@OSAPR01MB3315.jpnprd01.prod.outlook.com> <3a86118c1f8047c7932edae7d70fbf7d@XCH-RCD-001.cisco.com>
In-Reply-To: <3a86118c1f8047c7932edae7d70fbf7d@XCH-RCD-001.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; OSAPR01MB3745; 6:NAIQlSyErcXDUjaTqpzqKUW7YVCxqE7PxA5BSBOD0mpvzMpd6Qx+SxBIJKUNtEAHCvRii4boe8EJCAGgxIFmiukTtJZnIY7xhZ0dZ4YFZg7h2grYIolyzf0DuPIzaM97nLUnH/wkvu2oV9JLGNj+3ds87loIkhRd8mjEOJEjBTX9C2P2+OTf6zW/yEBgARBqeR4fo8wqshZAYhg5KCvZutrHFMR9ksojxPESUMcpfqw4YHrBXRvBZNYurA7ZV9K2Bchzv/Hz2cGWO0CIJKUaeIPVC1g0spwFym/ylYWHYKUOncwxtboCJSDHMjpRR4epup30bTj/cRT/DiKoPMlDpnEjYX2e54g3letCkLfCcGRTZEBFaBwgoPv89LRnlwX+xIRH9bScJIVwEX3F4cX8WRSILmcwo7ymtJCkANeUr874pvX+gRzYXWIyUEAYSJIjGgRLqzUhP0dA0qNTvHNZDA==; 5:dAJRysVvp2l88fZmJmYUFDGGXup7pwYyWMwMCeO2tpSIkDrcivHEDQiD8bJVjgoW3bCd745i5HrMklh80Y3T6slW816JLTIDJoQ+Czx27BqBkBcSuVwyf2SPzTjwsA6Oat771etetHFExouvujnvwV+kRw28gsy1Jm0k7Z49KlA=; 7:SdN650FvLfphjK7gkiXHSNU/EbwNOLiAPXPpro4C0jYxGtldrcKTMvW4WtlmQqu1CMqlDmbqIr1GgydRrilLttwgz7hVPFQLnpj4BGSBOIsZ6mjAO82pt1aVAK8wocKReNxncjWWPKu2d5Vd/EYhtw==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 0edc9bbe-9f07-4534-db27-08d664c6ec9c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:OSAPR01MB3745;
x-ms-traffictypediagnostic: OSAPR01MB3745:
x-microsoft-antispam-prvs: <OSAPR01MB3745D2E43586C9D3D91BCB0EE5BD0@OSAPR01MB3745.jpnprd01.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(3230021)(999002)(5005020)(6040522)(2401047)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231475)(944501520)(52105112)(148016)(149066)(150057)(6041310)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:OSAPR01MB3745; BCL:0; PCL:0; RULEID:; SRVR:OSAPR01MB3745;
x-forefront-prvs: 08902E536D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(136003)(39860400002)(366004)(346002)(13464003)(189003)(199004)(51874003)(99286004)(3846002)(2501003)(6116002)(305945005)(76176011)(316002)(102836004)(66066001)(6246003)(966005)(446003)(478600001)(105586002)(11346002)(9686003)(3480700005)(6306002)(5660300001)(110136005)(33656002)(8936002)(26005)(106356001)(476003)(6506007)(186003)(486006)(55016002)(14454004)(229853002)(256004)(14444005)(53936002)(53546011)(7736002)(66574012)(97736004)(68736007)(25786009)(2906002)(71190400001)(8676002)(71200400001)(6436002)(81156014)(81166006)(7696005)(86362001)(74482002)(74316002)(7756004); DIR:OUT; SFP:1101; SCL:1; SRVR:OSAPR01MB3745; H:OSAPR01MB3315.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: toshiba.co.jp does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 50sw80NnD8PYGSm5RbGq89wtd/dkoHTOt+2BDDGhBkXBdFWKswlgwpykkrbGGgFI7y3z78+ZWI8rF7jxflOv9cha+k2/mF9JdYgMVOt2JcI4sUj297CC0d1dKtrUH5iVOlASuGBVmtAlr1ebLaN/+wyXW2ve+o1jypSy2HUIJNzfi1ki7DkuejAL5GcVXGxMw9yDnLDbN78W2Z9eOZJrMO/xCguhPrab7/obM+y/JMxzcBrFtxWtEHqEV/VKVnK2YHLxBp9OQm0dklYb0T8ugqkqXLUoLRFrdmtGHOxrRVooBMUqe1AegLqGNe3Rchah
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: 0edc9bbe-9f07-4534-db27-08d664c6ec9c
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2018 08:58:05.5196 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f109924e-fb71-4ba0-b2cc-65dcdf6fbe4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSAPR01MB3745
MSSCP.TransferMailToMossAgent: 103
X-OriginatorOrg: toshiba.co.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/PTh7cAdI-AjgfsnwW8z4jTkD-NA>
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 08:58:18 -0000

Thanks for your response, Pascal.

Spinning off from 6tisch is a good starting point, I think. And
if we are using non-IP encapsulation, we need so many components
to discuss and 6tisch WG cannot cover that.


> The IESG is polling for BoF requests for Prague. Would you be interested in seeing that happen?

Yes, I'm very interested in PAW BoF!


Best regards,
Toshio Ito

> -----Original Message-----
> From: Pascal Thubert (pthubert) <pthubert@cisco.com>
> Sent: Tuesday, December 18, 2018 4:59 PM
> To: ito toshio(伊藤 俊夫 ○RDC□NSL) <toshio9.ito@toshiba.co.jp>; paw@ietf.org
> Subject: RE: Towards a PAW WG
> 
> Great question, Toshio : )
> 
> The architecture of 6TiSCH is global but the work there always focused on IPv6 (best effort) over 15.4 TSCH.
> I do not see 6TiSCH rechartering for DetNet type.
> I see PAW as a spin off from 6TISCH, focusing on the deterministic side of the 6TiSCH architecture, and
> extending to other MAC/PHYs, e.g., work starting at 802.11 in RTA/EHT.
> 
> And yes, I see PAW taking over the deterministic wireless data model work that started in 6TiSCH and stalled
> there. That is the last point below. We also have to consider what the detnet data plane formats becomes
> in a GMPLS environment where the flow ID and possibly the sequence can be implicit, derived from the timeslot.
> 
> The IESG is polling for BoF requests for Prague. Would you be interested in seeing that happen?
> 
> Pascal
> 
> > -----Original Message-----
> > From: toshio9.ito@toshiba.co.jp <toshio9.ito@toshiba.co.jp>
> > Sent: mardi 18 décembre 2018 08:46
> > To: Pascal Thubert (pthubert) <pthubert@cisco.com>; paw@ietf.org
> > Subject: RE: Towards a PAW WG
> >
> > 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