Re: [Iotops] New Version Notification for draft-sweet-iot-acme-01.txt

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 18 April 2022 14:48 UTC

Return-Path: <sarikaya2012@gmail.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 6C9073A1138 for <iotops@ietfa.amsl.com>; Mon, 18 Apr 2022 07:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level:
X-Spam-Status: No, score=-1.856 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 hiw6ndXleNkN for <iotops@ietfa.amsl.com>; Mon, 18 Apr 2022 07:48:10 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 2B96C3A113D for <iotops@ietf.org>; Mon, 18 Apr 2022 07:48:10 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id n17so12130793ljc.11 for <iotops@ietf.org>; Mon, 18 Apr 2022 07:48:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=FM0omPmViVt4zLjzhEFEU3popBULA46UBkyWs6FQamM=; b=GeeTFhhfTCgxBxpJXYRqhxkIqErstSIDh5Z5xRHDBLrsHOX8raeIAvzR6E8XY+01DA 0cbf3K6WYpwhGhaAoNLSugCDq7irN5SFupmARcWsvwmIqHdk74HVlg3yGuxcO1JmMfRs iAlNS0wJTzq7g6Xkw6WNW4eXmEd+zm2w/f+rzMkDRTenkMwnJQ5Z7g8NNKLemeRuBmQC im4kprFrQKilJkK7sg/4gz41JokuyC+DGqs79j0sZe/TJQZCAVasxX9kZpZqv1SxWO/r D11y+rqhSKDEpWp6jtFiXJenj3FbQiJDQ73cRaoOkhXU3n9FokUAo7QHB6ME9NCvA+0K pgzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=FM0omPmViVt4zLjzhEFEU3popBULA46UBkyWs6FQamM=; b=sgMlQzUEBV6nGBe0aXn7dC3IVVzz5F5HxCTT4yaO6MTIuX2E9a/UuR+aJEb8FK4cIB N07h5tNqHNtrUBrxzB6dd8P+fdgukjURyR1lyhUD1E8L+V9Ncad1Ntqey9weQ6Tc41xq va8SY3ow8ESkuVE98da4ZCJH6E2EU2N9IgAnSDUa+uO+RayHGm8pV6iQC4YyUMObKJtJ cyANt8dOwz0odY8PkOj8zDSOQMwOBz6ZeTlrbaiICj6ilS9pLYPl1Vb0wkwV+432hzT/ DBSvSFZDgP7rFPLiYRBqBEXmXblyb20LQfp21MTdJlseXL+oCgZIOh/CCd80aGAbfhrg VnmQ==
X-Gm-Message-State: AOAM53353NkLfY8yMDSJq0sY6ijYOBBlm2rF5x6FhNow3wEH5TV0pCzs hNY9Tl7uM2Y+BMA+fwC/Rru6u7YxPSaqUEwEaWU=
X-Google-Smtp-Source: ABdhPJyJbwkmFjYEhnD2lEJ8yv/qw1D+S6a0Hz6+tto1s64tNErPU454DarzQS/B/MHzuUPdO3o6cjgiryQQiN+8sQw=
X-Received: by 2002:a2e:9e11:0:b0:24c:5677:8b20 with SMTP id e17-20020a2e9e11000000b0024c56778b20mr7596076ljk.430.1650293287345; Mon, 18 Apr 2022 07:48:07 -0700 (PDT)
MIME-Version: 1.0
References: <164995026847.2586.16228265434075815549@ietfa.amsl.com> <DEF8E159-557F-4184-AA17-5F2E95522AEB@msweet.org> <CAC8QAcfZ3UC90te5=rHN6nWSDMVOiuNrYAbVknd=-HP9wY5=PA@mail.gmail.com> <1869DE73-A799-437D-BB0E-750383CB411A@msweet.org>
In-Reply-To: <1869DE73-A799-437D-BB0E-750383CB411A@msweet.org>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 18 Apr 2022 09:47:56 -0500
Message-ID: <CAC8QAcf7gcaKdyro=HAav4P7xajHkZnmO4O2c8Mt_ZbwUMepzA@mail.gmail.com>
To: Michael Sweet <msweet@msweet.org>
Cc: Behcet Sarikaya <sarikaya@ieee.org>, iotops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002ae21205dceed99a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/EPYdQaTPRnwHWRskropqk-WIyTU>
Subject: Re: [Iotops] New Version Notification for draft-sweet-iot-acme-01.txt
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 18 Apr 2022 14:48:16 -0000

On Fri, Apr 15, 2022 at 11:50 AM Michael Sweet <msweet@msweet.org> wrote:

> Behcet,
>
> > On Apr 15, 2022, at 11:13 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
> wrote:
> >
> > Hi Michael,
> >
> > I don't understand why wireless cable modem is an IoT device but lights,
> appliances at home are not IoT devices and ACME doesn't seem to apply to
> them?
>
> Sorry, did I say that?
>
> I do know that the CoRE WG is working on supporting constrained
> environments (lights, switches, etc.) which might not have the resources
> for ACME, but nothing in my draft would exclude them.  Most appliances I
> have experience with manage their own Internet connection (typically setup
> via a mobile app) that can do ACME.  Switches and lights typically use the
> Zigbee protocol and depend on a bridge device to provide Internet access,
> and the bridge device can do ACME.
>
> The focus of my draft is just to define the requirements for a local ACME
> server, how to discover it, and how to use it to provide a higher level of
> trust for IoT devices.
>
>
Yes, this is what I understood. But I think the example or use case you
chose defeats it.
Why would I need a certificate of the wireless cable model. just get the IP
address and use it.
So my suggestion is to revise the draft to better keep the focus like you
said above and explain it with a better example.

Behcet

> ________________________
> Michael Sweet
>
>
>
>