[6tsch] report flow contents

Thomas Watteyne <watteyne@eecs.berkeley.edu> Thu, 05 September 2013 18:41 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 5F2B121F9FED for <6tsch@ietfa.amsl.com>; Thu, 5 Sep 2013 11:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.876
X-Spam-Level:
X-Spam-Status: No, score=-1.876 tagged_above=-999 required=5 tests=[AWL=0.101, 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 kt1U3Mt6rCJQ for <6tsch@ietfa.amsl.com>; Thu, 5 Sep 2013 11:41:36 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 78E7F11E80FB for <6tsch@ietf.org>; Thu, 5 Sep 2013 11:41:36 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb10so2293722pad.9 for <6tsch@ietf.org>; Thu, 05 Sep 2013 11:41:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=QXNibCiUXvqX9TytekrvRIWegz8SNipfs00YNCJhKso=; b=yP8wfXnaQuodF5SAFAweUOo8DRLOhjC/nH0Byl0Qe6Zns7xBn+UYf1DUcUeW1SToxE KYMmw0AeOI2g9dflaNgV1v8tft7ycxIawww1ucvCLMzvqRHiGoWKa5hkDl+XxzZqxfLk tTGQLIsDzuw6rHchpi8BodUigc5qTgfghuKQNtErzOc5QeznFqHGAue3LT0nRe/nXfxA k0xMKC4MzlVqCgwQjXr6X9JGazDsU3Q5NG3SebY2hYSB193s9f/q68XiojhswnnulSst AsTffumCXIwmoJs3BDG8tw3c+K+ANLBviURTpZcOY6ORAHYc2rNoVAMMrmyP8pBad/sQ tYMw==
X-Received: by 10.68.98.101 with SMTP id eh5mr10777212pbb.65.1378406496189; Thu, 05 Sep 2013 11:41:36 -0700 (PDT)
MIME-Version: 1.0
Sender: twatteyne@gmail.com
Received: by 10.66.147.193 with HTTP; Thu, 5 Sep 2013 11:41:16 -0700 (PDT)
From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
Date: Thu, 5 Sep 2013 11:41:16 -0700
X-Google-Sender-Auth: qrUSK2slteRWOdNfx7VtD0GPQ4c
Message-ID: <CADJ9OA_XeC7Z5hFxyHhFGqD0aFMcBn=iHzDfRq34sL9qPi2P4A@mail.gmail.com>
To: "6tsch@ietf.org" <6tsch@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b6dd1008fc7a104e5a74556
Subject: [6tsch] report flow contents
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: Thu, 05 Sep 2013 18:41:37 -0000

*[renamed thread]*

Xavi,

A few thoughts:
- the counters (numTx, etc) will only be present for neighbors the node has
communicate with, so they should be optional in the packet.
- you have focused on the topological information (which I think is the
right one). It might be useful to gather other data related to
synchronization or queuing.
- I couldn't agree more with your suggestion to make it extensible. This
does mean that we will need to state somewhere that a device need to ignore
silently fields it does not understand.

Thomas

On Thu, Sep 5, 2013 at 11:15 AM, Xavier Vilajosana Guillen <
xvilajosana@eecs.berkeley.edu> wrote:

> Hello, I guess that flows are getting defined and I started to think on
> the contents of the messages on that flows. Not sure if this is the right
> time or I am going way far..
>
> According to the previous discussion I assume that the five flows are:
>
> ME-6TOP - Query Flow
> ME-6TOP - Action Flow
>
> 6TOP - ME - Report Flow
> 6TOP - ME - Event Flow
> 6TOP - ME - Request BW Flow
>
> I'd like to start defining the content of the messages in the Report Flow:
>
> The Report Flow: has to deal with the information that a node knows and
> has to be sent to the ME so the ME can compute the schedule among others.
> Here I list  the information that we can know in a mote and can be used at
> the ME to compute the schedule (complete please if I miss something)
>
> For each known neighbor:
>  -ID
>  -AVG RSSI in a running window
>  -Latest RSSI
>  -Num TX packets
>  -Num ACK packets
>  -Num RX packets
>  -Last ASN when it heart about that neighbor
>
> Other fields
>  -Num links in the Schedule to that neighbor
>     -For each link PDR
>
>
> Then we need to have some TLV like objects that can be used for
> ad-hoc/naive/other extensions of the reporting process. In that way we
> don't constraint the implementation of the scheduling alg. to that
> information.
>
> what do you think?
> X
>
>
> On Fri, Aug 30, 2013 at 10:45 AM, Qin Wang <qinwang@berkeley.edu> wrote:
>
>> Hi all,
>>
>> In this thread, we will continue the discussion about Confirmation
>> message. Here is some background information.
>>
>> Context: e.g.
>>     - node sends a report and want to know if the report is accepted.,
>>     - ME sends a action request and want to know if/when the action taken.
>> Options:
>>    (1) Nothing
>>    (2) Rely on transport mechanism (e.g. confirmable CoAP message)
>>    (3) App-level ACK type
>>    (4) Use different flow (i.e. action flow)
>>
>> IMHO, different control flow may have different requirement for
>> confirmation message.
>>     (1) Action Flow, needs a App-level confirmation, like Succ/Fail
>>     (2) Query Flow, automatically has the confirmation, i.e. the message
>> packet corresponding to a specific query.
>>      (3) Report Flow and Event Flow, option (1)-(3) are OK, but I prefer
>> option (1) and (3), i.e. the confirmation message is an option, but if a
>> confirmation message is needed, it should be App-level Ack, instead of
>> transport layer confirmation, which will give 6top more flexibility.
>>
>> What do you think?
>>
>> Thanks
>>  Qin
>>
>>
>> _______________________________________________
>> 6tsch mailing list
>> 6tsch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tsch
>>
>>
>
> _______________________________________________
> 6tsch mailing list
> 6tsch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tsch
>
>