Re: [Iotops] draft-moran-iot-nets direction

Eliot Lear <lear@lear.ch> Thu, 13 October 2022 18:15 UTC

Return-Path: <lear@lear.ch>
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 E271BC15271E for <iotops@ietfa.amsl.com>; Thu, 13 Oct 2022 11:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
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 a9BDhxuxCtFo for <iotops@ietfa.amsl.com>; Thu, 13 Oct 2022 11:15:22 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 C7630C157B48 for <iotops@ietf.org>; Thu, 13 Oct 2022 11:15:21 -0700 (PDT)
Received: from [IPV6:2001:420:c0c0:1001::16d] ([IPv6:2001:420:c0c0:1001:0:0:0:16d]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 29DIFG5p2333693 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 13 Oct 2022 20:15:18 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1665684918; bh=x84/M3yAZc5QCRtRe3xU8hci4OlHyEFNK8DHnoNGjQk=; h=Date:Subject:From:To:References:In-Reply-To:From; b=LdS+8Y3Myw69LYneOqYwOg8BjTk2XqFLrnwvg7fvNcptpJy/KrOOUgDIme0iLe822 s//m8lrBjJrhBpn4nr/uKHup8RWBEXyW/dsh0CXj3ugwhwwGr9tEdGeKQD4QtiakHf AvnnAp5kxaK+SqpHYDNhlhtTGObWY0sdUbuqaBko=
Message-ID: <ee39b765-f891-f272-327c-917ed18527ea@lear.ch>
Date: Thu, 13 Oct 2022 20:15:15 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.13.1
Content-Language: en-US
From: Eliot Lear <lear@lear.ch>
To: Brendan Moran <brendan.moran.ietf@gmail.com>, iotops@ietf.org
References: <CAPmVn1OmmH441Ehr6FPTZ8Do0w_jQAwGhf6ZEAaqqLEpdVztsg@mail.gmail.com> <bb207a5f-c2ec-9cee-83de-6bfc0d03592d@lear.ch>
In-Reply-To: <bb207a5f-c2ec-9cee-83de-6bfc0d03592d@lear.ch>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------Ggl2LMIOofktJmt4Yi2GZG0t"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/eV6ym2oEdY7nrccqEJrvMFY86NE>
Subject: Re: [Iotops] draft-moran-iot-nets direction
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, 13 Oct 2022 18:15:27 -0000

Sorry about that.  Meant to reply to sender.

On 13.10.22 20:13, Eliot Lear wrote:
> You are fast.  We should find time to have a breakfast in London.
>
> On 13.10.22 16:54, Brendan Moran wrote:
>> After the discussion at the iotops virtual interim, the plan I have
>> for the future direction of draft-moran-iot-nets is to convert it to a
>> mapping from baseline requirements and threats described in existing
>> baseline security requirements documents (e.g. ENISA, ETSI, NIST) to
>> ietf technologies and to point out any gaps.
>>
>> Where threats are not described it might be useful to add 
>> ietf-specific threats.
>>
>> I plan to develop this before IETF115.
>>
>> Best Regards,
>> Brendan
>>
>