Re: [core] Designs to resolve streaming issues in SenML

Carsten Bormann <cabo@tzi.org> Wed, 13 January 2016 14:31 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B281B2E31 for <core@ietfa.amsl.com>; Wed, 13 Jan 2016 06:31:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fIr_NmqmyFjC for <core@ietfa.amsl.com>; Wed, 13 Jan 2016 06:31:13 -0800 (PST)
Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA80A1B2E33 for <core@ietf.org>; Wed, 13 Jan 2016 06:31:12 -0800 (PST)
Received: from mfilter48-d.gandi.net (mfilter48-d.gandi.net [217.70.178.179]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 4FDB9FB8D4; Wed, 13 Jan 2016 15:31:11 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter48-d.gandi.net
Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter48-d.gandi.net (mfilter48-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id bfaPoSzheYh5; Wed, 13 Jan 2016 15:30:39 +0100 (CET)
X-Originating-IP: 134.102.17.180
Received: from eduroam-0436.wlan.uni-bremen.de (eduroam-0436.wlan.uni-bremen.de [134.102.17.180]) (Authenticated sender: cabo@cabo.im) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id DBE6EFB8E1; Wed, 13 Jan 2016 15:30:38 +0100 (CET)
Message-ID: <56965F8D.9040309@tzi.org>
Date: Wed, 13 Jan 2016 15:30:37 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <175A1806-ACB0-4FC7-A318-2A58FF66CDD2@cisco.com>
In-Reply-To: <175A1806-ACB0-4FC7-A318-2A58FF66CDD2@cisco.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/-cJxJbRrTc3kx-a4Rgur03oGy8w>
Cc: core <core@ietf.org>
Subject: Re: [core] Designs to resolve streaming issues in SenML
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 14:31:14 -0000

Cullen Jennings (fluffy) wrote:
> pro / cons of the -03 design vs -04 design.

One comment I made when this was discussed in Yokohama was that the -04
design makes the processor examine every single measurement record
whether there is a change to the base values (and, if there are only
changes to base values so that record isn't really a measurement
record).  That might impede high speed processing a bit.  E.g., it could
become harder to merge two time sequences because each single entry in
them might be changing a base value that is relevant to entries in the
other stream.  But I haven't implemented either model, so that is just a
hunch.

Apart from that kind of consideration, that part of the approach -04 is
pretty much equivalent to -03.

Grüße, Carsten