Re: [core] [Last-Call] Last Call: <draft-ietf-core-senml-more-units-02.txt> (Additional Units for SenML) to Proposed Standard

Carsten Bormann <cabo@tzi.org> Tue, 22 October 2019 15:50 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C94120145; Tue, 22 Oct 2019 08:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 bdI7rRZyH_oL; Tue, 22 Oct 2019 08:50:13 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A2D71200E7; Tue, 22 Oct 2019 08:50:13 -0700 (PDT)
Received: from [192.168.217.110] (p5089AE1C.dip0.t-ipconnect.de [80.137.174.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46yHyW4M1MzySN; Tue, 22 Oct 2019 17:50:11 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2466ABB9-374F-459F-AF6F-3E1FF38F6262@episteme.net>
Date: Tue, 22 Oct 2019 17:50:11 +0200
Cc: Cullen Jennings <fluffy@iii.ca>, last-call@ietf.org, core-chairs@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, draft-ietf-core-senml-more-units@ietf.org
X-Mao-Original-Outgoing-Id: 593452209.385865-e1671ccef4f53aeffa15a70caec5bfc7
Content-Transfer-Encoding: quoted-printable
Message-Id: <672CC672-67B4-42BF-8570-14B8EE4A4213@tzi.org>
References: <157124774214.7822.2416155258603633472.idtracker@ietfa.amsl.com> <C17F33E0-E060-4104-B9DD-6F48CCC9EF27@iii.ca> <2466ABB9-374F-459F-AF6F-3E1FF38F6262@episteme.net>
To: Pete Resnick <resnick@episteme.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/nZfs7CV4eIkng8pXdIYKsRdbiYQ>
Subject: Re: [core] [Last-Call] Last Call: <draft-ietf-core-senml-more-units-02.txt> (Additional Units for SenML) to Proposed Standard
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 22 Oct 2019 15:50:16 -0000

On Oct 22, 2019, at 17:33, Pete Resnick <resnick@episteme.net> wrote:
> 
> Implementations are perfectly capable of multiplying and adding.

I think after 40+ years in the industry I can refute that statement :-)

But, seriously, this draft is based on a specific request from an SDO, OMA/IPSO, for which this secondary registry would enable porting their existing data models to ones based on the SenML units registry.  Other SDOs from this space might follow suit.

Clearly, when we did SenML, we didn’t want to go this route.  Currently, there is an amazing pull towards data model harmonization that has changed the fundamentals enough that this draft now makes sense.  I’ll leave it to IPSO people to explain this in more details.

“MAY, but SHOULD NOT” means exactly what it says; I don’t think there is a contradiction.
But of course we can contract this to “SHOULD NOT” if that helps.  Oh, and “cm” isn’t registered yet because OMA didn’t need it, not because it couldn’t be registered if that turns out to be desirable.

SenML is now in a position to play a centerpiece in the harmonized IoT data landscape.  Not going for this draft is likely to thwart this opportunity.

Grüße, Carsten