IETF Logo Mail Archive

Re: [core] Benjamin Kaduk's Discuss on draft-ietf-core-senml-14: (with DISCUSS and COMMENT)

Michael Koster <michaeljohnkoster@gmail.com> Sat, 12 May 2018 21:15 UTC

Return-Path: <michaeljohnkoster@gmail.com>
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 6A2AA12E8E7; Sat, 12 May 2018 14:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Qb2DBYnl9s1Q; Sat, 12 May 2018 14:15:31 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DD1712EACD; Sat, 12 May 2018 14:15:31 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id b130-v6so7599105oif.12; Sat, 12 May 2018 14:15:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RVR4SDNuIXG7JZoDxzu8aTMJ0pGPhBw/yQmG0Rz199Y=; b=Kjgoh3kZ6jBBdfm42yyT7ZZmkCn7xM+/+Zb93BJFb6s5cf+3h2djsG0mMgCCLvAeEt BikXsDGhI9vVWe/maC+/LMICuqGBwQHiLKvzPjPx6Kj6QTU1zLphObfnfrqMEHpqfzML 5EZzHohc8WFPctrG/y8IyhnJgiWtl5jYpKf4fM089dXiJsyX+zghjclaFlvKIANp8f/5 ReF866SJK3EHcDDbqr2JqtKc4zW9JG9EGHHe2pl60ruyyflvnpa3CoYS89SvhpiW7ess gLezSlBzuCC1KMmEYH2Bgy7W1u4gR1BNUj0vCsGn9ktvk1zyDxrLRi47vdh6Ki1XaRlb gvGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RVR4SDNuIXG7JZoDxzu8aTMJ0pGPhBw/yQmG0Rz199Y=; b=tv/6bvs+63pwf7gOjEcuQvD7P4+F+GRGqTUzHpklxHJWilYPpz6NIlWlXqZWJFv9i9 rYsEEwZohKMyLJ9y1YW5a3L1nUAf0B7NEjKdAF3yPsVeocutRzjxWEJFKvFEiINU6UH6 MAYrn4jvPAH6dmYPCiD1+kNgeTlLI9tFJqs/ncs+ZrTBFl04X0q+UJKSZ3gttEm2rn79 5IuOgM0tf+PXZULErJ7ZfuqAR+Af4VImaAGJDjXdhx6nbzSiSrhwRZCuddBdjmYXlaBX V8TXfUJnrF7gu7oXJ98+Lvxue4WtcNQ3zuTN7XBkZy/V2ixQqnclffs22Bs/iLV5ZZR8 sJ3Q==
X-Gm-Message-State: ALKqPwd5hxyPe271Ftc7RpKqFaupu7xH1xWoFOPWuqIRlHUbptMA5YmG Udh8c7GBLt+3x4IIz2hqgNc=
X-Google-Smtp-Source: AB8JxZqmQlk405Lv6t/IWZ02F3HJRRvOYwcgqMfJdvxLwSwNLFQYlT+H+KDTTXsz2/UC/RP7bYYATA==
X-Received: by 2002:aca:eb4c:: with SMTP id j73-v6mr2862752oih.109.1526159730611; Sat, 12 May 2018 14:15:30 -0700 (PDT)
Received: from [10.0.0.3] (108-201-184-41.lightspeed.sntcca.sbcglobal.net. [108.201.184.41]) by smtp.gmail.com with ESMTPSA id b45-v6sm4100848otb.55.2018.05.12.14.15.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 12 May 2018 14:15:29 -0700 (PDT)
From: Michael Koster <michaeljohnkoster@gmail.com>
Message-Id: <7FD83B7D-DB09-4198-9DE6-26A0F5F1B2D9@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_14411A1F-C535-4C86-9CD5-31271070A044"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 12 May 2018 14:15:22 -0700
In-Reply-To: <3C64FC4D-B771-4B43-BC19-DE7BD1132173@fastmail.fm>
Cc: Ari Keränen <ari.keranen@ericsson.com>, "core-chairs@ietf.org" <core-chairs@ietf.org>, "draft-ietf-core-senml@ietf.org" <draft-ietf-core-senml@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>, core <core@ietf.org>, The IESG <iesg@ietf.org>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
References: <152410519508.28821.948642754454286088.idtracker@ietfa.amsl.com> <84E57656-B191-4DB4-B7EC-97059D5B19DE@ericsson.com> <20180508000154.GY84491@kduck.kaduk.org> <44DB4CCE-62E7-43FF-9E0B-9AF27E14EE87@tzi.org> <0C881DE7-7991-4E3C-A8C8-B77AEC2F55CC@ericsson.com> <3C64FC4D-B771-4B43-BC19-DE7BD1132173@fastmail.fm>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/MAbXlTemrXjpc7EMgNqfgcZQirA>
Subject: Re: [core] Benjamin Kaduk's Discuss on draft-ietf-core-senml-14: (with DISCUSS and COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 12 May 2018 21:15:33 -0000

+1

Michael Koster

> On May 12, 2018, at 2:02 PM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
> 
> Hi Ari,
> 
> On 11 May 2018, at 20:05, Ari Keränen <ari.keranen@ericsson.com <mailto:ari.keranen@ericsson.com>> wrote:
> 
>> Hi all,
>> 
>> While addressing the IESG review comments regarding the use of time in SenML we came up with a simple way to enable SenML Records to express also relative times in the future that would have minimal impact to any existing use of SenML. We could use the following definition:
>> 
>>   Values greater than or equal to 2**28 represent an absolute time relative to the Unix epoch. Values less than 2**28 represent time relative to the current time.
>> 
>> That is, instead of only values less than zero, also values less than 2**28 (268,435,456) would be used to express relative time. Negative values and zero are still times in past and "now" respectively, as before. Time values from zero to 2**28 would be relative times in the future.
>> 
>> The only change this causes in the current use of SenML is that the smallest absolute time expressible in SenML becomes 1978-07-04 21:24:16 UTC instead of 1970-01-01 00:00 UTC. The absolute times after 1978 are still exactly the same ("Seconds after Unix epoch"). We are not aware of any deployments with SenML data between 1970 and 1978 that would be impacted negatively by this. 
>> 
>> For details, see:
>> https://github.com/core-wg/senml-spec/pull/129/files <https://github.com/core-wg/senml-spec/pull/129/files>
>> 
>> Would anyone have concerns about including this change in SenML before publication?
>> 
>> Since we are already very late in the process and we need to get SenML published as RFC very soon, we would also need to agree on this very soon.
> 
> No objections from me personally, but please double check with the WG.
> 
> Best Regards,
> Alexey
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email