Re: [6tsch] Dynamic slot activation (was part of the 4th control flow)

Xavier Vilajosana Guillen <xvilajosana@eecs.berkeley.edu> Thu, 29 August 2013 20:00 UTC

Return-Path: <xvilajosana@berkeley.edu>
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 6F87E21F9C88 for <6tsch@ietfa.amsl.com>; Thu, 29 Aug 2013 13:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 MOMLV4BcHeOh for <6tsch@ietfa.amsl.com>; Thu, 29 Aug 2013 13:00:28 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 29CF721F9BF3 for <6tsch@ietf.org>; Thu, 29 Aug 2013 13:00:27 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fz6so1363295pac.31 for <6tsch@ietf.org>; Thu, 29 Aug 2013 13:00:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=P8kan+G2jHvBYIW8SzQ2fqzt/SEe8HjkGQCtfBp79i4=; b=BPLQlbbMYEcV+tUijJGup7GzsBv/0MC5rmCX4ZADouK1PwP2FKPsydsBXHjirTK9QO OZ/lH6RA62ER2k0Gl6lG06sXRFhxfQf+v8SIwyWS/Fb4SawE77QugiYbSM6zcst/ul4q BXxRQ/QeOf0q0vuaxKWjCj+OCPjv3+LN9Tmgg6YnYbD2pjHRQDckV0x+6ZXGc9IOakH8 /4UfJllOiGRwhjjV6NL8icXAIy+9iQk7C7sZ7VNKOC1+0c/K650v/6BD1GM9LghjENCJ /dpOFwOxNukr+vKuv851cLl034ferjDcbfzkKM6Nkcsv3y9EFhUP0S3+LIbgxnMjG8AC xr5w==
X-Gm-Message-State: ALoCoQkv1v5Hg9q87zM9B3R8u1VNLhzdu8/7DdwHNPG5nuDre7wVec4u2Hynw3G3iBC9pa1RMLmw
MIME-Version: 1.0
X-Received: by 10.68.194.161 with SMTP id hx1mr5475440pbc.164.1377806425910; Thu, 29 Aug 2013 13:00:25 -0700 (PDT)
Received: by 10.70.34.44 with HTTP; Thu, 29 Aug 2013 13:00:25 -0700 (PDT)
In-Reply-To: <CADJ9OA87bCD69oXF1RgbjSNgNYs8r9Mj-1fNithSYheJ2OXy+Q@mail.gmail.com>
References: <E045AECD98228444A58C61C200AE1BD84143010E@xmb-rcd-x01.cisco.com> <CADJ9OA9aLyRe-Us6kkpXs0SsWwhBV6XsqvPQfg5iNbv6COuYWg@mail.gmail.com> <CAAzoce5EJ+9xcrEkm098dSfbYvSBGE3syFEZfNEBW_Xy9MVWFw@mail.gmail.com> <CADJ9OA87bCD69oXF1RgbjSNgNYs8r9Mj-1fNithSYheJ2OXy+Q@mail.gmail.com>
Date: Thu, 29 Aug 2013 13:00:25 -0700
Message-ID: <CALEMV4aAWpY=uN+exOMFXd0iA1_3pyetG+J34A4ShJXJ5KbJUA@mail.gmail.com>
From: Xavier Vilajosana Guillen <xvilajosana@eecs.berkeley.edu>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Content-Type: multipart/alternative; boundary="047d7b10d1ef96001e04e51b8e4e"
Cc: Maria Rita PALATTELLA <maria-rita.palattella@uni.lu>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "6tsch@ietf.org" <6tsch@ietf.org>, Qin Wang <qinwang@berkeley.edu>, "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
Subject: Re: [6tsch] Dynamic slot activation (was part of the 4th control flow)
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: xvilajosana@eecs.berkeley.edu
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: Thu, 29 Aug 2013 20:00:35 -0000

ok, I like it. If there is no objection I will change the name to minimal
6TiSCH

cheers.
Xavi



On Thu, Aug 29, 2013 at 12:52 PM, Thomas Watteyne <
watteyne@eecs.berkeley.edu> wrote:

> Of course!
>
>
> On Thu, Aug 29, 2013 at 12:11 PM, Qin Wang <qinwang@berkeley.edu> wrote:
>
>> Can we just call it "minimal 6TiSCH", instead of "minimal 6TiSCH
>> configuration"?
>>
>> Qin
>>
>>
>> On Fri, Aug 30, 2013 at 2:41 AM, Thomas Watteyne <
>> watteyne@eecs.berkeley.edu> wrote:
>>
>>> +1
>>>
>>> Rather than "basic", let's talk about "minimal 6TiSCH Configuration",
>>> i.e. the title of the draft.
>>>
>>> Xavi agreed a couple of calls ago to rename
>>> "draft-vilajosana-6tsch-basic" to "draft-vilajosana-6tisch-minimal"
>>>
>>> Thomas
>>>
>>>
>>> On Thu, Aug 29, 2013 at 2:16 AM, Pascal Thubert (pthubert) <
>>> pthubert@cisco.com> wrote:
>>>
>>>>  Hello Xavi and Qin:****
>>>>
>>>> ** **
>>>>
>>>> I’m not sure we want  to continue this discussion now or keep it for
>>>> later, but either way I’m making it a separate thread to save the current
>>>> conclusions.****
>>>>
>>>> ** **
>>>>
>>>> In short, Thomas below asked:****
>>>>
>>>> ** **
>>>>
>>>> *Thomas> over what cells with the reports travel? Another questions
>>>> could be: over what cells will the request to install cells travel?*
>>>>
>>>> ** **
>>>>
>>>> This is a good question and at the same time this is not really
>>>> something that we have to answer right now, per our proposed charter, as
>>>> Xavi indicates:****
>>>>
>>>> *Xavi> I think it is better first to concentrate on the basic things*
>>>>
>>>> ** **
>>>>
>>>> On the side I think the use of the word ‘basic’ these days could create
>>>> confusion since it seems to refer to draft-vilajosana-6tsch-basic which is
>>>> probably not Xavi’s intention here.****
>>>>
>>>> I’d suggest that when we refer to the operation in the
>>>> draft-vilajosana-6tsch-basic draft, we call it something like “Basic
>>>> 6TiSCH” or “Basic 6TiSCH Support” so the use of the plain word “basic” may
>>>> not be confusing anymore.****
>>>>
>>>> ** **
>>>>
>>>> For this particular thread, I suggested as an answer to Thomas that 1)
>>>> I agree that in the future the control flows could travel over a Basic
>>>> 6TiSCH instance, and in that case 2) that we could probably handle
>>>> burstiness of control traffic by overprovisioning time slots and then
>>>> indicating dynamically which extra time slots are being used; as Qin puts
>>>> it very clearly:****
>>>>
>>>> *Qin> Over-provision can increase the throughput at peak time, while
>>>> the control bits can reduce the energy consumption for idle-listening (at
>>>> least at the beginning of slot) in those unused Tx/Rx cells.*
>>>>
>>>> I was thinking of something like a ‘more’ bit in a cell the is being
>>>> used in order to tell listeners to wake up in the next overprovisionned
>>>> cell, as opposed to a bit sent at the beginning of the overprovisionned
>>>> cell that would indicate that the cell is not being used, though. Xavi
>>>> agrees that it *Xavi> sounds to me a great idea*****
>>>>
>>>> ** **
>>>>
>>>> To make sure that we do not make a confusion between 1) the bits that
>>>> control the use of overprovisionned cells in a bundle and that are pigy
>>>> backed with the traffic to indicate there is more trafficoutstanding and 2)
>>>> the end to end protocol that controls the allocation of cells between a
>>>> controlling entity and the device, or between devices, JP insisted that the
>>>> control flows for the latter (which are the subject of the original thread
>>>> by Qin) should be cleanly defined and that we should not expect to piggy
>>>> back them with traffic:****
>>>>
>>>> *JP> I would just be vary cautious when thinking of piggybacking
>>>> control information in packet header for control plane purpose***
>>>>
>>>> ** **
>>>>
>>>> With this summary, it is up to us to continue the discussion or save it
>>>> for later. Should we continue, I suggest we do it in the context of Basic
>>>> 6TiSCH to see if that mode could benefit from over-provisioned time slots
>>>> but then provide a way to use only a subset of those slots. This would
>>>> probably make Basic 6TiSCH a lot more useful in the future for applications
>>>> of various scales and degrees of burstiness.****
>>>>
>>>> ** **
>>>>
>>>> Cheers,****
>>>>
>>>> ** **
>>>>
>>>> Pascal****
>>>>
>>>
>>>
>>
>