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

Ben Campbell <ben@nostrum.com> Fri, 18 May 2018 16:34 UTC

Return-Path: <ben@nostrum.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 0F2CF12DA24; Fri, 18 May 2018 09:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 MnbOR4FPdVU8; Fri, 18 May 2018 09:34:55 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 CAEBF12D7F6; Fri, 18 May 2018 09:34:55 -0700 (PDT)
Received: from [10.18.10.6] (ip-105-232-239-173.texas.us.northamericancoax.com [173.239.232.105]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w4IGYiKF016903 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 18 May 2018 11:34:51 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-105-232-239-173.texas.us.northamericancoax.com [173.239.232.105] claimed to be [10.18.10.6]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <CCD2D740-AFDF-44D3-8258-D751BEFA8FA5@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A3A2A4DD-FB6B-4AC9-9D3D-C17A312683E9"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Fri, 18 May 2018 10:34:50 -0600
In-Reply-To: <FC1AD855-6A06-460B-A688-8CB69A973E09@ericsson.com>
Cc: core <core@ietf.org>, Jaime Jiménez <jaime.jimenez@ericsson.com>, "core-chairs@ietf.org" <core-chairs@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-core-senml@ietf.org" <draft-ietf-core-senml@ietf.org>
To: Ari Keränen <ari.keranen@ericsson.com>
References: <152385571314.20985.5160681583375127961.idtracker@ietfa.amsl.com> <FC1AD855-6A06-460B-A688-8CB69A973E09@ericsson.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/GMxjZclWcFKY_zAmsN0KtHmbCpI>
Subject: Re: [core] Ben Campbell'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: Fri, 18 May 2018 16:34:57 -0000

Hi Ari, please see comments inline. I’ve removed sections that don’t seem to need further discussion.

> On May 7, 2018, at 11:52 AM, Ari Keränen <ari.keranen@ericsson.com> wrote:
> 


>> Hopefully this is easy to address:
>> 
>> §4.7  talks about how SenML can also be used to configure parameters and
>> controlling actuators. That capability has some rather significant security
>> implications, but I failed to find mention of it in the security
>> considerations. That needs to be explicitly discussed.
> 
> Now Section 13 mentions actuator use explicitly:
> 
>  When SenML is used for configuration or
>  actuation, it can be used to change the state of systems and also
>  impact the physical world, e.g., by turning off a heater or opening a
>  lock.
> 
>  The SenML formats alone do not provide any security and instead rely
>  on the protocol that carries them to provide security.  Applications
>  using SenML need to look at the overall context of how these formats
>  will be used to decide if the security is adequate.  In particular
>  for sensitive sensor data and actuation use it is important to ensure
>  that proper security mechanims are used.

That is sufficient to clear my discuss.

However, I suggest adding something to the following effect to the first paragraph:

“Malicious use of SenML to change system state could have severe consequences, potentially including violation of physical security, property damage, and even loss of life."

[…]