[6tisch] slot schedluing

Randy Turner <rturner@amalfisystems.com> Wed, 07 December 2016 20:39 UTC

Return-Path: <rturner@amalfisystems.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8CE50129BD5 for <6tisch@ietfa.amsl.com>; Wed, 7 Dec 2016 12:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SSVHbAarOUrg for <6tisch@ietfa.amsl.com>; Wed, 7 Dec 2016 12:39:58 -0800 (PST)
Received: from atl4mhob15.myregisteredsite.com (atl4mhob15.myregisteredsite.com []) by ietfa.amsl.com (Postfix) with ESMTP id BC9EA129B48 for <6tisch@ietf.org>; Wed, 7 Dec 2016 12:39:11 -0800 (PST)
Received: from mailpod.hostingplatform.com ([]) by atl4mhob15.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id uB7KdA1O028801 for <6tisch@ietf.org>; Wed, 7 Dec 2016 15:39:10 -0500
Received: (qmail 26593 invoked by uid 0); 7 Dec 2016 20:39:10 -0000
X-Authenticated-UID: rturner@amalfisystems.com
Received: from unknown (HELO ? (rturner@amalfisystems.com@ by 0 with ESMTPA; 7 Dec 2016 20:39:10 -0000
From: Randy Turner <rturner@amalfisystems.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Message-Id: <A1BBF4F4-4530-4B7B-BD94-D3A3669DE878@amalfisystems.com>
Date: Wed, 07 Dec 2016 15:37:09 -0500
To: 6tisch@ietf.org
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/3OQPPrS_5IF0FqwpOl3CrDYqHbw>
Subject: [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: Wed, 07 Dec 2016 20:39:59 -0000

Hi All,
Just re-confirming an assumption — from a TSCH perspective, slot scheduling assumes any single transmission “cannot” exceed a slot boundary — if transmissions require a certain amount of time, then the slot width is increased to deal with this ( or possibly increase the TX bit rate if possible )

Is this correct ?