Re: [6tisch] slot schedluing

worley@ariadne.com (Dale R. Worley) Fri, 16 December 2016 15:07 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860F312965F for <6tisch@ietfa.amsl.com>; Fri, 16 Dec 2016 07:07:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 8YAKC0-9MUdF for <6tisch@ietfa.amsl.com>; Fri, 16 Dec 2016 07:07:26 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8821C129546 for <6tisch@ietf.org>; Fri, 16 Dec 2016 07:07:26 -0800 (PST)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-11v.sys.comcast.net with SMTP id Hu67cwMAf6nWCHu6XcEIRA; Fri, 16 Dec 2016 15:07:25 +0000
Received: from hobgoblin.ariadne.com ([24.60.114.4]) by resomta-ch2-06v.sys.comcast.net with SMTP id Hu6VcEXnrBjCGHu6Wc8B5w; Fri, 16 Dec 2016 15:07:25 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id uBGF7MM1030815; Fri, 16 Dec 2016 10:07:22 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id uBGF7Kna030801; Fri, 16 Dec 2016 10:07:20 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Tero Kivinen <kivinen@iki.fi>
In-Reply-To: <22611.57176.745566.641512@fireball.acr.fi> (kivinen@iki.fi)
Sender: worley@ariadne.com
Date: Fri, 16 Dec 2016 10:07:20 -0500
Message-ID: <871sx7q5ef.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfPBUAfEOYIuCnGdmZ0uuPW951rZdr9vV7hOwtD8CSGJ/iR3RcdaGdBXleXCXsgs5E/BXxY/bIM/uJCO7/dX0GjudTLSeOxqrR+C65UGRtjLo+yrrzBDf 3cLa0NsB3PtYrubeS2+tTX0KChfSiUNWO1PyZOQX/Fq1ohNF49qyedLfJastlLX+/i1h6Dmte9Ic9lT5yF6Psm2W0EDi9WmJQHWRqi1vCewnfEKzB4QHQ7xO Fq+V6FlM8pKsuNzok7TrLqxiV8OeAc0JCX46sld5tr2w+OKpFsEft4TuaqUXj4pg
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/01rGpS7uFK6oKadApBATMhvSmy0>
Cc: 6tisch@ietf.org, pthubert@cisco.com, rturner@amalfisystems.com, thomas.watteyne@inria.fr
Subject: Re: [6tisch] slot schedluing
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2016 15:07:32 -0000

Tero Kivinen <kivinen@iki.fi> writes:
> IEEE Std. 802.15.4-2015 EB can be up to any length that the PHY will
> support. In the normal 2.4GHz O-QPSK PHY this is 127 bytes.
>
> Other PHYs do have other limits, and for example the 802.15.4t
> "Amendment: Higher Rate (2 Mb/s) Physical (PHY) Layer" will support
> max frame size of 2048 bytes on the same 2.4GHz band (with higher data
> rate).

So that's the keys, different PHYs have different link-level framing,
and some allow longer packets.

I assume that if using one of those PHYs, the time slots are still long
enough for any frame (within the limits allowed by the PHY and network
configuration).

> In the 802.15.10 "Recommended Practice for Routing Packets in IEEE
> Std 802.15.4 Dynamically Changing Wireless Networks" which provides
> mesh networking and routing to the 802.15.4 they will include several
> IEs in EBs, and EBs are separated so that some EBs have TC IEs, some
> have NLM IEs and so on. And because NLM IEs can still be too large,
> they will send them in pieces, i.e., the NLM IE contains internal
> subsetting, where they send the whole list of neighbors over multiple
> NLM IEs. 

That's interesting, as it sounds like 802.15.10 will put the routing
protocol will be done at the link level rather than within IPv6.  Is
this aligned with the work ROLL is doing, or is it an alternative?

Dale