[OPSAWG] DNS in IoT devices -- draft-richardson-opsawg-mud-iot-dns-considerations-03

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 17 December 2020 18:35 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1009C3A0E6E; Thu, 17 Dec 2020 10:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 dV8w994UDQIY; Thu, 17 Dec 2020 10:35:16 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F5D33A0E6D; Thu, 17 Dec 2020 10:35:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id AA5C3389AC; Thu, 17 Dec 2020 13:38:00 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rhoCJCauHvAb; Thu, 17 Dec 2020 13:38:00 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 40983389A8; Thu, 17 Dec 2020 13:38:00 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9CCFF11B4; Thu, 17 Dec 2020 13:35:14 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: mud@ietf.org, opsawg@ietf.org, iotops@ietf.org
In-Reply-To: <27659.1608229409@localhost>
References: <27659.1608229409@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 17 Dec 2020 13:35:14 -0500
Message-ID: <30840.1608230114@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/H7dfLbfNIfmPII7V1gLeOW_-Ahs>
Subject: [OPSAWG] DNS in IoT devices -- draft-richardson-opsawg-mud-iot-dns-considerations-03
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2020 18:35:18 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > 3) Operational Considerations for use of DNS in IoT devices
    > draft-richardson-opsawg-mud-iot-dns-considerations-03
    > Abstract
    > This document details concerns about how Internet of Things devices
    > use IP addresses and DNS names.  The issue becomes acute as network
    > operators begin deploying RFC8520 Manufacturer Usage Description
    > (MUD) definitions to control device access.

    > This document explains the problem through a series of examples of
    > what can go wrong, and then provides some advice on how a device
    > manufacturer can best make deal with these issues.  The
    > recommendations have an impact upon device and network protocol
    > design.

This document is a BCP, and it creates no new protocol or on-the-wire-bits.

It may be an appropriate document for IOTOPS if OPSAWG does not wish to work
on it.  Actually, I'm more and more convinced that this is an important
aspect for an IETF architectural view on IoT.

The ADD WG chairs examined it, as it has policy about when (not) to use
DoT/DoH/QuadX-Do53, but determined that it was not in the rather narrow ADD
charter.

I would like to get early review from DNSOP, and I will endeavour to get that
early in the new year.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide