[6tsch] mechanism to config Report

Qin Wang <qinwang@berkeley.edu> Tue, 10 September 2013 14:32 UTC

Return-Path: <qinwang@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 04D6411E81BB for <6tsch@ietfa.amsl.com>; Tue, 10 Sep 2013 07:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level:
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=0.903, 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 GgF8X6t9boX3 for <6tsch@ietfa.amsl.com>; Tue, 10 Sep 2013 07:32:53 -0700 (PDT)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id D81B111E81B8 for <6tsch@ietf.org>; Tue, 10 Sep 2013 07:32:52 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id 17so7356552iea.1 for <6tsch@ietf.org>; Tue, 10 Sep 2013 07:32:52 -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:date:message-id:subject:from:to :content-type; bh=PNcN44y/Btk2aw/6Ic8ZEK408MV75jPbvFdAviNFtCI=; b=eQBzE17ZU4aP7rWC2yDwONGJzKh6MUIz70gNSgIz0QvoBC/5n+xqYBN+ZqxQj/MMmG 2aKqtHbppzKElPPoim0lzcy1VFii1wJbwu3MtK/Z9k1mhZRUu3hRU4fpwSJHkgV8MXir +tY6MJSrRZbvfxelfXoy48Mb9rM/6aotw7cqZaqqB1OnIkTA3ZB9jxoDbT6xO/NYKk4M pGTeH5dTaDuPujQiy3BMLvuIjIH31OLOchvSgmRtfZoHNAo1E8e4kCvyQNdkQL2mzh9D k+8olYYeaJ7LNvG5JzcfIC6Jcgv9J2+3TVl+A7D+VmTRCuowL/u5GqbHkQlR+DJByybV oHfQ==
X-Gm-Message-State: ALoCoQk2IdF2ICKB/1IjrW2X3nm3bJtaE/kR6Uq9k6t8wBJpQSxz/qXcVgIcHr7hTHZ2dqvN5j7r
MIME-Version: 1.0
X-Received: by 10.50.20.195 with SMTP id p3mr10942706ige.26.1378823572315; Tue, 10 Sep 2013 07:32:52 -0700 (PDT)
Received: by 10.64.139.234 with HTTP; Tue, 10 Sep 2013 07:32:52 -0700 (PDT)
Date: Tue, 10 Sep 2013 22:32:52 +0800
Message-ID: <CAAzoce7MLsNXS0Ra3NZph3Y1eovRf13vUOG54kYqG9=cEoWDOw@mail.gmail.com>
From: Qin Wang <qinwang@berkeley.edu>
To: "6tsch@ietf.org" <6tsch@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bd74b6a3c6ea004e6086109
Subject: [6tsch] mechanism to config Report
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: Tue, 10 Sep 2013 14:32:58 -0000

Hi all,

We have had a lot of discussion in thread "report flow contents". As you
see, there are many items, but I believe not all of them will be needed in
same time base or under same criteria. Thus, a mechanism to config Reports
by PCE via Action flow is needed. Here is sort of solution I want to
propose.

(1) think the contents listed by Xavi in thread "report flow contents" as a
part of MIB, and add a configuration field to each attribute, denoted as
 ReportCriteria.

(2) define ReportCriteria as a tuple (Criteria, CriteriaValue) . For
example,
Criteria =TIME, CriteriaValue=500, means reporting in every 500ms.
Criteria = Index of RSSI attribute, CriterValue = some Threshold, means
reporting when RSSI is worse than the Threshold.

(3) In implementation, the ReportCriteria field in MIB will implemented as
events which drive Report Flow and Event Flow.

What do you think? Any input is welcome.

Thanks
Qin