IETF Logo Mail Archive

Re: [Iotops] WG Adoption Call on draft-moran-iot-nets-02

Russ Housley <housley@vigilsec.com> Thu, 02 March 2023 23:06 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36060C151AE9 for <iotops@ietfa.amsl.com>; Thu, 2 Mar 2023 15:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_hm_y3SioO4 for <iotops@ietfa.amsl.com>; Thu, 2 Mar 2023 15:06:27 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2079C14CE38 for <iotops@ietf.org>; Thu, 2 Mar 2023 15:06:27 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 705DC18DF8C; Thu, 2 Mar 2023 18:06:26 -0500 (EST)
Received: from [10.0.1.2] (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 5ED8218D2DC; Thu, 2 Mar 2023 18:06:26 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1744680.1677792579@dyas>
Date: Thu, 02 Mar 2023 18:06:26 -0500
Cc: iotops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6174B4C8-697B-464B-AB02-6DAEF3910B94@vigilsec.com>
References: <2b042daf-a7a4-84b4-bd9a-bb293849ca43@isode.com> <2C446A21-E61A-408A-99EA-5B3B34CA9AFA@vigilsec.com> <1744680.1677792579@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/9avkWeGCfEuTpXUMM3mNX4n70k0>
Subject: Re: [Iotops] WG Adoption Call on draft-moran-iot-nets-02
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Mar 2023 23:06:33 -0000

Michael:

> Russ Housley <housley@vigilsec.com> wrote:
>> I have no objection to the adoption of this document, but I would like
>> to see the discussion also cover protection of data at rest in the IoT
>> device.  Currently, it talks about "information in transit on the
>> networks or stored in the IoT application or in the Cloud."  However,
>> the protections for data at rest are not really covered in the
>> subsections that follow.
> 
> While I agree that this is important, I am not entirely certain it's within
> the IETF's mandate :-)
> That doesn't mean we shouldn't do it though, but it may be too big a bite.

We have mechanisms that were defines for store-and-forward communications that will work.  Just use them.

Russ

v2.23.0 | Report a Bug | By Email