[Mud] MUD file for DNS probes, avoiding non-public address space

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 20 September 2019 17:18 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 6D4CD120099 for <mud@ietfa.amsl.com>; Fri, 20 Sep 2019 10:18:55 -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 u3RbnnIoBTFK for <mud@ietfa.amsl.com>; Fri, 20 Sep 2019 10:18:53 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CA2D120130 for <mud@ietf.org>; Fri, 20 Sep 2019 10:18:53 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0887B3897B for <mud@ietf.org>; Fri, 20 Sep 2019 13:17:08 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4F361F5 for <mud@ietf.org>; Fri, 20 Sep 2019 13:18:52 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: mud@ietf.org
X-Attribution: mcr
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: Fri, 20 Sep 2019 13:18:52 -0400
Message-ID: <31565.1568999932@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mud/HixLBARP0y45EBHWGyz7kJNuvgw>
Subject: [Mud] MUD file for DNS probes, avoiding non-public address space
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, 20 Sep 2019 17:18:55 -0000

The RIPE Atlas probes do distributed DNS monitoring.
There is a lot that a MUD file could do to restrict other unwanted traffic,
even if we have to write an ACL allowing traffic to 0.0.0.0/0 port 53.

In IPv6, it's more properly 2000::/3 port 53, which nicely rules out
DNS traffic to ULAs, link-locals, multicast, mapped IPv4 and default NAT64
space, etc.
{If 4000::/3 gets deployed by IANA, I think we'll have decades of notice}

Maybe 0.0.0.0/0 should really read:
  0.0.0.0/5     (0.0.0.0 -> 7.255.255.255)
  8.0.0.0/7     (8.0.0.0 -> 9.255.255.255)
                omitted 10.0.0.0/8
  11.0.0.0/8
  12.0.0.0/6
  16.0.0.0/4
  32.0.0.0/3
  64.0.0.0/3    (64.0.0.1 - 95.255.255.254)
  96.0.0.0/6    ... you get the idea.

quite annoyance.

So, what we want is to whitelist 0.0.0.0/0 and then blacklist RFC1918 and
100.64.0.0/10, and class D space.  (maybe not class E space)
I have to back to the document to remember if we can actually do plus and
minus, etc.

Maybe there should be a macro for this?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-