Re: [Paw] Towards a PAW WG

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 18 December 2018 07:59 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 54EBC130E70 for <paw@ietfa.amsl.com>; Mon, 17 Dec 2018 23:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.959
X-Spam-Level:
X-Spam-Status: No, score=-15.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, 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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 LTNLT7z2i6oz for <paw@ietfa.amsl.com>; Mon, 17 Dec 2018 23:59:28 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDB6F1310B8 for <paw@ietf.org>; Mon, 17 Dec 2018 23:59:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7182; q=dns/txt; s=iport; t=1545119967; x=1546329567; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=fPaQfUeIkQQeLbZ7yrh6kfuQqYMD6Ynbh/WS3peR7eA=; b=kT3dw7lO8v6p6/R2APz322v7MwcKJZaV+CRt4p/ij1LWwER/P5dum8fR gmPkREXWCFWi9OO7tFp2B39hRp2v0kWVezCGtbSAwvoWwcyOn2FbU1Jas RKje/b34mDZ3UQxavMq5P547KVCV4r+NPF8iRTn/CPKYyDsnkp39olUp0 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAADNpxhc/5hdJa1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwIBAQEBAQsBggNmgQInCoNylBKCDYNFlBUUgWcLAQEYC4RJAheDBSI2Bw0BAwEBAgEBAm0cDIU8AQEBBAEBIRE6AhUEAgEIEQEDAQEDAiYCAgIlCxUCBggCBAESCIMbggAPp3WBL4QxAoYDBYELizQXgUA/gRGCFH6DHgEBA4EiBE+CcYJXAok0BodmkAEJAocNikgggV2FHopZiHUJQ4R2ixACERSBJyYLJoFWcBU7gmyCJxeIXoU/QTGNYIEfAQE
X-IronPort-AV: E=Sophos;i="5.56,367,1539648000"; d="scan'208";a="496716463"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Dec 2018 07:59:26 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id wBI7xQ8O020515 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 18 Dec 2018 07:59:26 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 18 Dec 2018 01:59:25 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Tue, 18 Dec 2018 01:59:25 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "toshio9.ito@toshiba.co.jp" <toshio9.ito@toshiba.co.jp>, "paw@ietf.org" <paw@ietf.org>
Thread-Topic: Towards a PAW WG
Thread-Index: AQHUk6+CJdcPwKK/iUaZBR0bVQ3vMqWEJUNQ////9/A=
Date: Tue, 18 Dec 2018 07:59:14 +0000
Deferred-Delivery: Tue, 18 Dec 2018 07:59:09 +0000
Message-ID: <3a86118c1f8047c7932edae7d70fbf7d@XCH-RCD-001.cisco.com>
References: <E50B14E5-58F7-42C7-B58E-4E3660E6AD53@cisco.com> <OSAPR01MB3315C25D4E9E9EC3D4A71983E5BD0@OSAPR01MB3315.jpnprd01.prod.outlook.com>
In-Reply-To: <OSAPR01MB3315C25D4E9E9EC3D4A71983E5BD0@OSAPR01MB3315.jpnprd01.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.252.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/4g2cMT1-HGVb3dWVw0-4sGnXp2o>
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:59:30 -0000

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