IETF Logo Mail Archive

Re: [6tsch] Mobility in 6TSCH

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Sat, 27 July 2013 09:41 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFC621F9E02 for <6tsch@ietfa.amsl.com>; Sat, 27 Jul 2013 02:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1O8xeQ0zx7DX for <6tsch@ietfa.amsl.com>; Sat, 27 Jul 2013 02:41:43 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 446C321F9DF1 for <6tsch@ietf.org>; Sat, 27 Jul 2013 02:41:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12187; q=dns/txt; s=iport; t=1374918103; x=1376127703; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Q2LDj2ooJaNv2pi4Yz7cbElNbFCes9fcNFaXx5btLJA=; b=MMa/lklKP/kU5gEl+ejCrK8X+0mwIVrUIfi5D50jzdtS7zt5rIQ2clIu I6i3hrumzN9HxAPzOUQryLqLbMVZVfvUK0YX9WtmnaRBGcoU8UnGuNkhv b+fxiky4ZT3PVY4/ZIsjIPnQUWwnn8c84cbXVkkGqHCFc/s69I6nfBLXV E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAEGV81GtJXG9/2dsb2JhbABaDoI0RDVQvVyBFhZ0giQBAQEEAQEBKkELEAIBCBEEAQELHQcnCxQJCAEBBAEJBAUIiAgMuCsBAwaOQoEELQQGAYMWbwOFRKNnglY+gWhC
X-IronPort-AV: E=Sophos; i="4.89,756,1367971200"; d="scan'208,217"; a="240222009"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 27 Jul 2013 09:41:42 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6R9ffoH022328 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 27 Jul 2013 09:41:41 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.94]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Sat, 27 Jul 2013 04:41:41 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Alfredo Grieco <alfredo.grieco@gmail.com>, Thomas Watteyne <watteyne@eecs.berkeley.edu>
Thread-Topic: [6tsch] Mobility in 6TSCH
Thread-Index: Ac6KG/JDReFusAQHRyi92NDFFsbTgAANov2AABz8VQAAANbgAAAHOz7g
Date: Sat, 27 Jul 2013 09:41:41 +0000
Deferred-Delivery: Sat, 27 Jul 2013 09:41:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD8413AC97F@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD8413ABB1B@xmb-rcd-x01.cisco.com> <CAAzoce4v=7m18FhJij8-H+2Di3EFcEyEY=1c18__HgVLTkf1tQ@mail.gmail.com> <CADJ9OA8aCJwcipo6CdMQL_n_ru+QCqPTDqYXTVxKE2x5pZBqJg@mail.gmail.com> <CAM4EQiPSAPrftt6AM30r4YENA_vJ1huQzvVeOMnBnmKne0ea9w@mail.gmail.com>
In-Reply-To: <CAM4EQiPSAPrftt6AM30r4YENA_vJ1huQzvVeOMnBnmKne0ea9w@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.217.27]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD8413AC97Fxmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: "6tsch@ietf.org" <6tsch@ietf.org>
Subject: Re: [6tsch] Mobility in 6TSCH
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
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" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jul 2013 09:41:48 -0000

Dear all;

I love the term "relocation".
We probably want a relocation that is transparent to the upper layers.
The topology can also be qualified as relatively stable.

What do others think?

Cheers,

Pascal

From: 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org] On Behalf Of Alfredo Grieco
Sent: samedi 27 juillet 2013 10:04
To: Thomas Watteyne
Cc: 6tsch@ietf.org
Subject: Re: [6tsch] Mobility in 6TSCH

Almost static topologies ?

Alfredo

On Saturday, July 27, 2013, Thomas Watteyne wrote:
Pascal,

I understand you are looking for the right term.

Terms I can think of:
- roaming
- node relocation
- occasional mobility
- intermittent relocation

Thomas

On Fri, Jul 26, 2013 at 7:50 PM, Qin Wang <qinwang@berkeley.edu<javascript:_e(%7b%7d,%20'cvml',%20'qinwang@berkeley.edu');>> wrote:
Hi Pascal and All,

How about "dynamic adjustment". Because,

In steady network (fixed location and predictable traffic load),  the features of deterministic and low energy consumption have definitely been provided. What we want to do is, with distributed reservation and RPL, the deterministic and low energy consumption features can be extended to the dynamic network (some degree of location change and/or some degree of traffic load change).

Thought?

Qin



On Sat, Jul 27, 2013 at 12:20 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<javascript:_e(%7b%7d,%20'cvml',%20'pthubert@cisco.com');>> wrote:
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 mailing list
6tsch@ietf.org<javascript:_e(%7b%7d,%20'cvml',%20'6tsch@ietf.org');>
https://www.ietf.org/mailman/listinfo/6tsch


_______________________________________________
6tsch mailing list
6tsch@ietf.org<javascript:_e(%7b%7d,%20'cvml',%20'6tsch@ietf.org');>
https://www.ietf.org/mailman/listinfo/6tsch

v2.8.7 | Report a Bug | By Email