Re: [6tsch] work item 2 in the charter
Thomas Watteyne <watteyne@eecs.berkeley.edu> Sun, 21 July 2013 21:28 UTC
Return-Path: <twatteyne@gmail.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 82A9C11E8102 for <6tsch@ietfa.amsl.com>;
Sun, 21 Jul 2013 14:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level:
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=0.048,
BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 RMwvf5GyvAhI for
<6tsch@ietfa.amsl.com>; Sun, 21 Jul 2013 14:28:20 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com
[IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id
A390211E80A5 for <6tsch@ietf.org>; Sun, 21 Jul 2013 14:28:20 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id uo1so6318811pbc.3 for
<6tsch@ietf.org>; Sun, 21 Jul 2013 14:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:from:date
:x-google-sender-auth:message-id:subject:to:content-type;
bh=HewfC4m/WsVwb9nJMlSFPEoQL39CACSaRwvD3NlV+zQ=;
b=Fgnq8vu6ZzwQdhhowN8U1wUA0GZsXb1wqfve07sYZXzW4kXxXqLideyepIYGp+nfDj
K14j5PP8W7Uga0vkXDOe3oEtDJmLV37Jh8U4/RX2wAre+DjSTTwlq1z/D14lmvBETnol
nFkA3THuQiNC4YfUl6xI8trh02HRVZbZYJa0+Zkm/ANfQlwXajNZ3jbQ+FOtamHBi6MC
avru4UjfV4JUiKD0n8LnkrXkdK5aFB0dHHyR0aY/bguCCnlKKy+JQ1kJzOx7ksx1PdhC
xAL5N4nritLJaG26bHrXp7IWwGgfkfbbkue876UjG9P9yKY3JMA7nTT83MM4ZK2CO5wG qUSg==
X-Received: by 10.68.186.193 with SMTP id fm1mr27263715pbc.163.1374442100388;
Sun, 21 Jul 2013 14:28:20 -0700 (PDT)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.66.147.228 with HTTP; Sun, 21 Jul 2013 14:28:00 -0700 (PDT)
In-Reply-To: <CAAzoce514e=PouvHNuvJy5Wn+gWb4=XC-5p4r9aGs7qE-96aNA@mail.gmail.com>
References: <E045AECD98228444A58C61C200AE1BD84137DB02@xmb-rcd-x01.cisco.com>
<CAAzoce7GEpnviwKkqC61hWx2Bkx8Y1f72UBq3c03PV6FfPgEKw@mail.gmail.com>
<E045AECD98228444A58C61C200AE1BD84137E60E@xmb-rcd-x01.cisco.com>
<CAAzoce514e=PouvHNuvJy5Wn+gWb4=XC-5p4r9aGs7qE-96aNA@mail.gmail.com>
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Sun, 21 Jul 2013 23:28:00 +0200
X-Google-Sender-Auth: RxSorNzqi45mn5g1DkxtVo6OP_g
Message-ID: <CADJ9OA-cQeRhK0SgV-9urYzZdxnQ76NWnoXEJKEikK2itaazzQ@mail.gmail.com>
To: 6TSCH <6tsch@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bd764b2287b5004e20c3dd4
Subject: Re: [6tsch] work item 2 in the charter
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: Sun, 21 Jul 2013 21:28:21 -0000
Qin, all, We've had a lot of discussion around mobility during the webex calls a couple of months ago. I'm looking at the call from 3/22 in particular, the minutes of which are at [1] and the recording at [2]. We ended up identifying 2 cases where some nodes are mobile: - nodes mounted on a crane. Either the crane is pivoting, or two cranes cooperate to pick containers up. - a mobile worker We agreed that there were a number of tricks we could play to accommodate some mobility: - for the crane case, Alfredo suggested that we could "have [the] same cells scheduled at several potential neighbors of the node mounted on the crane" - for the mobile worker case, Tom suggested that "mobile worker does not require deterministic schedules". In light of that, I would like to suggest to not over-promise on mobility. That is, we think we have a good solution for building static network, and that there are some tricks we can play for making space for some mobility. Yet, the solution we come up with involve some communication to resolve topological changes, either with a PCE, or locally using some reservation protocol. Since there is some delay/overhead associated with that, they are not designed for e.g. swarms of mobile robots. I'm not saying TSCH is not a good idea for swarms of robot, rather that we first focus on (almost) static networks. Maybe I'm missing your point. If I am, could you write down the exact rewording of the charter you are suggesting, and maybe point out the exact use cases? Thanks, Thomas [1] https://bitbucket.org/6tsch/meetings/wiki/130322_webex [2] https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=66940742&rKey=711b58d40cd574d9 On Sunday, July 21, 2013, Qin Wang wrote: > Pascal, > > Yes, I think we can add "mobility" in the first paragraph of "Description > of Working Group [2/5]". > > Thanks > Qin > > > On Sat, Jul 20, 2013 at 2:55 PM, Pascal Thubert (pthubert) < > pthubert@cisco.com> wrote: > > Dear Qin:**** > > ** ** > > I’m a bit out of sync.**** > > ** ** > > 1) I agree we shoud have mobility somewhrere**** > > 2) slide 8 in the charter slides on the repo is this “ Description of > Working Group [2/5]”**** > > ** ** > > Is that where you’d like to see mobility mentioned?**** > > ** ** > > Cheers,**** > > ** ** > > Pascal**** > > ** ** > > *From:* Qin Wang [mailto:qinwang@berkeley.edu] > *Sent:* vendredi 19 juillet 2013 21:12 > *To:* Pascal Thubert (pthubert) > *Cc:* 6tsch@ietf.org > *Subject:* Re: [6tsch] work item 2 in the charter**** > > ** ** > > Hi Pascal,**** > > ** ** > > The slides are pretty good. Just a comment on slide-8. Should we add > "mobility" as one of criteria?**** > > ** ** > > Thanks**** > > Qin**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > On Sat, Jul 20, 2013 at 12:06 AM, Pascal Thubert (pthubert) < > pthubert@cisco.com> wrote:**** > > Dear all:**** > > **** > > Please review the latest draft of the charter at > https://bitbucket.org/6tsch/charter-ietf-6tsch/src **** > > Now is a good time to find the bugs! **** > > Work Item 2 in the charter ( > https://bitbucket.org/6tsch/charter-ietf-6tsch/) is still like this:**** > > **** > > “**** > > 2. Produce "6TSCH centrali > >
- [6tsch] work item 2 in the charter Pascal Thubert (pthubert)
- Re: [6tsch] work item 2 in the charter Thomas Watteyne
- Re: [6tsch] work item 2 in the charter Qin Wang
- Re: [6tsch] work item 2 in the charter Pascal Thubert (pthubert)
- Re: [6tsch] work item 2 in the charter Qin Wang
- Re: [6tsch] work item 2 in the charter Thomas Watteyne
- Re: [6tsch] work item 2 in the charter Pascal Thubert (pthubert)
- Re: [6tsch] work item 2 in the charter Thomas Watteyne
- Re: [6tsch] work item 2 in the charter Qin Wang
- Re: [6tsch] work item 2 in the charter Thomas Watteyne
- Re: [6tsch] work item 2 in the charter Pascal Thubert (pthubert)