[Mud] draft-richardson-opsawg-mud-iot-dns-considerations-00
Michael Richardson <mcr+ietf@sandelman.ca> Fri, 16 August 2019 00:54 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: mud@ietfa.amsl.com
Delivered-To: mud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3AE5120103 for <mud@ietfa.amsl.com>; Thu, 15 Aug 2019 17:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 EEUZH2y3UPWH for <mud@ietfa.amsl.com>; Thu, 15 Aug 2019 17:54:22 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 838451200F3 for <mud@ietf.org>; Thu, 15 Aug 2019 17:54:22 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A1E8E3818C for <mud@ietf.org>; Thu, 15 Aug 2019 20:53:31 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 52346788 for <mud@ietf.org>; Thu, 15 Aug 2019 20:54:21 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: mud@ietf.org
In-Reply-To: <156262380876.734.2268328972581793672.idtracker@ietfa.amsl.com>
References: <156262380876.734.2268328972581793672.idtracker@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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-sha256"; protocol="application/pgp-signature"
Date: Thu, 15 Aug 2019 20:54:21 -0400
Message-ID: <21721.1565916861@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/fdmjqkhkoOwSP0SigJZtsqMo15E>
Subject: [Mud] draft-richardson-opsawg-mud-iot-dns-considerations-00
X-BeenThere: mud@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Manufacturer Ussage Descriptions <mud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mud>, <mailto:mud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mud/>
List-Post: <mailto:mud@ietf.org>
List-Help: <mailto:mud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mud>, <mailto:mud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2019 00:54:25 -0000
Hi, I started a document just before the IETF105 cut-off https://datatracker.ietf.org/doc/draft-richardson-opsawg-mud-iot-dns-considerations/ the intention of which is to address how IoT devices use DNS. It's very drafty :-) I actually started the document again on Tuesday, forgetting where I'd place the first copy, and in it I used the term "specific purpose devices" rather than the more marketing "IoT" term. I don't want to fill in the solution part of the document yet, I'd prefer to make sure that I get the problem statement in the Introduction correct. Section 2: map names should deal with the different ways to map names using Do53. Section 3: should deal with pathologies that we see. For instance, using redirects to random CDN hostnames for access to firmware. Although I think that maybe these two sections along with part of the Intro should be in a Problem Statement section. Have I missed anything in the problem statement? How much introduction is in order so that DNS/DPRIVE and CDN types will understand this. 1. Introduction [RFC8520] provides a standardized way to describe how a specific purpose device makes use of Internet resources. Access Control Lists (ACLs) can be defined in an RFC8520 Manufacturer Usage Description (MUD) file that permit a device to access Internet resources by DNS name. Use of a DNS name rather than IP address in the ACL has many advantages: not only does the layer of indirection permit the mapping of name to IP address to be changed over time, it also generalizes automatically to IPv4 and IPv6 addresses, as well as permitting loading balancing of traffic by many different common ways, including geography. At the MUD policy enforcement point - the firewall - there is a problem. The firewall has only access to the layer-3 headers of the packet. This includes the source and destination IP address, and if not encrypted by IPsec, the destination UDP or TCP port number present in the transport header. The DNS name is not present! In order to implement this, there must be a mapping between the names in the ACLs and layer-3 IP addresses. The first section of this document details a few strategies that are used. The second section of this document details how common manufacturer anti-patterns get in the way this mapping. The third section of this document details how current trends in DNS resolution such as public DNS servers, DNS over TLS (DoT), and DNS over HTTPS (DoH) cause problems for the strategies employed. Poor interactions with content-distribution networks is a frequent pathology that results. The fourth section of this document makes a series of recommendations ("best current practices") for manufacturers on how to use DNS, and IP addresses with specific purpose IoT devices. The Privacy Considerations section concerns itself with issues that DNS-over-TLS and DNS-over-HTTPS are frequently used to deal with. The question is how these concerns apply to IoT devices located within a residence or enterprise is dealt with. The Security Considerations section covers some of the negative outcomes should MUD/firewall managers and IoT manufacturers choose not to cooperate. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Mud] draft-richardson-opsawg-mud-iot-dns-consideā¦ Michael Richardson