Re: [6tisch] slot schedluing

Tero Kivinen <kivinen@iki.fi> Fri, 16 December 2016 12:42 UTC

Return-Path: <kivinen@iki.fi>
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 17D4C129D69 for <6tisch@ietfa.amsl.com>; Fri, 16 Dec 2016 04:42:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 l61ciotNbliZ for <6tisch@ietfa.amsl.com>; Fri, 16 Dec 2016 04:42:27 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) (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 D3991129C16 for <6tisch@ietf.org>; Fri, 16 Dec 2016 04:42:26 -0800 (PST)
Received: from fireball.acr.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.15.2/8.15.2) with ESMTPS id uBGCg4pb005469 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Dec 2016 14:42:04 +0200 (EET)
Received: (from kivinen@localhost) by fireball.acr.fi (8.15.2/8.14.8/Submit) id uBGCg42S002703; Fri, 16 Dec 2016 14:42:04 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID: <22611.57628.580983.374526@fireball.acr.fi>
Date: Fri, 16 Dec 2016 14:42:04 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
In-Reply-To: <42ef462aa8604d81b328ec80a406fede@XCH-RCD-001.cisco.com>
References: <A1BBF4F4-4530-4B7B-BD94-D3A3669DE878@amalfisystems.com> <87twaedumh.fsf@hobgoblin.ariadne.com> <CADJ9OA-01L+m8vvrPaB-OwE9OEsB22X_udN5MasD2kvkrY-4ow@mail.gmail.com> <42ef462aa8604d81b328ec80a406fede@XCH-RCD-001.cisco.com>
X-Mailer: VM 8.2.0b under 24.5.1 (x86_64--netbsd)
X-Edit-Time: 7 min
X-Total-Time: 6 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/_xUP6_3ZcuSkS3Lnzh9b3zouMVI>
Cc: Randy Turner <rturner@amalfisystems.com>, "Dale R. Worley" <worley@ariadne.com>, "6tisch@ietf.org" <6tisch@ietf.org>, Thomas Watteyne <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 12:42:28 -0000

Pascal Thubert (pthubert) writes:
> Seems that large EBs at low rates ended up being a problem in subgig cases
> after all, Dale.
> 
> The discussion at the interim was either to make very large slots =>
> impractical, or preconfigure sometimes, 2 or more consecutive time slots are
> paired; the second is never scheduled, and is free to accept the remainder of
> the frame sent in the first… The pairing will be interesting to make work,
> ince the channel computation is based on ASN so the consecutive time slots to
> not have the same channel offset….

I do not think you can do that. 802.15.4-2015 section 6.7.5
Transmission timing restrictions specifies that you have allowed
transmission interval (ATI), and in TSCH that is TSCH timeslot, which
have specific start and stop times. Node is not allowed to go over
that, i.e., the transmission must be completed before the end of ATI,
and also if this is ACKed transmission the original sender must allow
enough time for the other end to send back the appropriate ACK frame
with required IEs (i.e. Time Synchronization in TSCH). There is also
guard time to make sure that even if someone starts early we do not
run over with previous transmission.
-- 
kivinen@iki.fi