Re: [6tisch] The channel hopping scheme seems to be suboptimal

worley@ariadne.com (Dale R. Worley) Fri, 23 September 2016 18:52 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 2397112B789 for <6tisch@ietfa.amsl.com>; Fri, 23 Sep 2016 11:52:15 -0700 (PDT)
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 M81ahK4iqG7o for <6tisch@ietfa.amsl.com>; Fri, 23 Sep 2016 11:52:14 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 33D7E12B76F for <6tisch@ietf.org>; Fri, 23 Sep 2016 11:52:13 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-07v.sys.comcast.net with SMTP id nVYubMGhsff8qnVa0bLr2Z; Fri, 23 Sep 2016 18:52:12 +0000
Received: from hobgoblin.ariadne.com ([73.100.16.189]) by resomta-ch2-20v.sys.comcast.net with SMTP id nVZzblrU2MDTinVa0b2lUr; Fri, 23 Sep 2016 18:52:12 +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 u8NIqB99019682; Fri, 23 Sep 2016 14:52:11 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u8NIqAIB019679; Fri, 23 Sep 2016 14:52:10 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Thomas Watteyne <thomas.watteyne@inria.fr>
In-Reply-To: <CADJ9OA_B_fGy3xu3Fr_zWDuxcdP1-3bx7j6DA3pxoUgXpJ3QAA@mail.gmail.com> (thomas.watteyne@inria.fr)
Sender: worley@ariadne.com
Date: Fri, 23 Sep 2016 14:52:10 -0400
Message-ID: <87shsqbg9x.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfIcA4sCTeGIPlEe3rh8cuR6z0Tkli962IRF4mN15JfmzTt8fceeboiQkJi6LAkotLiyI78ghJ07q7yP9w3Jdd3Xtke8Jmvb8MczMTybzGg+QlAJ4jloW sY7R7F1YeR6KWvF7SWKPoNr6k8XChtP7NHd0FsJI/ftkF3uGlkMjf7NUZjBWkLII70fj/k7EfQSEqCJ9dmBcVCwxjlEniMdF6A4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/sfWLo7A_nd0pKwWIrS-PLc6Z8DI>
Cc: 6tisch@ietf.org
Subject: Re: [6tisch] The channel hopping scheme seems to be suboptimal
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, 23 Sep 2016 18:52:15 -0000

Thomas Watteyne <thomas.watteyne@inria.fr> writes:
> You raise a valid point. There are a couple of points, though, that make an
> "Absolute Slot Number" more favorable compared to an "Absolute Slotframe
> Number":
> - if you schedule multiple cells between two nodes in a single slotframe,
> you want those different transmissions to happen at a different frequency

Although you could construct the schedule so that the nodes have
different channel offsets for the different slots within the schedule.

> - ASN is used to construct a nonce when securing link-layer frames.
> Security is such that we never want to re-use the same nonce.

Although you could construct the nonce to be (ASFN * nSlots +
slotOffset).  And you need to do a construction like that to make sure
that different nodes with different channel offsets during the same slot
do not use the same nonce.

I suspect the main reason is that several slotframe schedules of
different lengths can be active at the same time in one network.
Keeping a separate ASFN for each schedule would require a lot of work.

Dale