[6tsch] Mobility in 6TSCH

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 26 July 2013 16:21 UTC

From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6tsch@ietf.org" <6tsch@ietf.org>
Thread-Topic: Mobility in 6TSCH
Thread-Index: Ac6KG/JDReFusAQHRyi92NDFFsbTgA==
Date: Fri, 26 Jul 2013 16:20:40 +0000
Deferred-Delivery: Fri, 26 Jul 2013 16:20:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD8413ABB1B@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [6tsch] Mobility in 6TSCH
Precedence: list

Dear all;

As you know, determinism and fast mobility are quite antagonistic in nature. 

Even with distributed routing, there are a number of issues like timeslot allocation and security context transfer or (re)establishment that will delay the mobility.
In 6TSCH, we have use cases that we want to serve like the crane and the mobile handset, which require a certain degree of mobility but probably not make before break or sub-second reconnection. So we want to express that we aim at supporting this limited mobility but we do not want to raise the expectation higher than we can actually serve.

The mobility term is so overloaded that it might be misleading. Would you have a suggestion for term that would be more appropriate?

(I heard the terms soft, limited, and constrained so far)

Cheers,

Pascal

[6tsch] Mobility in 6TSCH Pascal Thubert (pthubert)
Re: [6tsch] Mobility in 6TSCH Qin Wang
Re: [6tsch] Mobility in 6TSCH Thomas Watteyne
Re: [6tsch] Mobility in 6TSCH Alfredo Grieco
Re: [6tsch] Mobility in 6TSCH Pascal Thubert (pthubert)
Re: [6tsch] Mobility in 6TSCH Xavier Vilajosana Guillen
Re: [6tsch] Mobility in 6TSCH Qin Wang