IETF Logo Mail Archive

Re: [OPSAWG] revisions in draft-ietf-opsawg-mud-iot-dns-considerations-01

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 06 April 2021 00:23 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 9EBDF3A2E38 for <opsawg@ietfa.amsl.com>; Mon, 5 Apr 2021 17:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 KAvuMh4_noIa for <opsawg@ietfa.amsl.com>; Mon, 5 Apr 2021 17:23:27 -0700 (PDT)
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 ECCD63A2E37 for <opsawg@ietf.org>; Mon, 5 Apr 2021 17:23:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 929E638E50; Mon, 5 Apr 2021 20:30:07 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6i9vXjrprtrw; Mon, 5 Apr 2021 20:30:07 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 363AB38E4F; Mon, 5 Apr 2021 20:30:07 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B9DCCE2; Mon, 5 Apr 2021 20:23:23 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tirumal reddy <kondtir@gmail.com>, opsawg <opsawg@ietf.org>
In-Reply-To: <CAFpG3gfWx4vZThF5GhA0Z57JjBUP0GVZUsuAsC=ST+H2GRmeOw@mail.gmail.com>
References: <ecd58332-3192-7dbf-9685-afddf9a5030e@sit.fraunhofer.de> <CAFpG3gcvsywDwNDEhY_savtp5Rx+JqTPfTcFRjge55x7LsNE_w@mail.gmail.com> <4395.1613948972@localhost> <CAFpG3gfWx4vZThF5GhA0Z57JjBUP0GVZUsuAsC=ST+H2GRmeOw@mail.gmail.com>
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: Mon, 05 Apr 2021 20:23:23 -0400
Message-ID: <3674.1617668603@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/gvgx4I0x2ldxhabpzbwC0pCHeAQ>
Subject: Re: [OPSAWG] revisions in draft-ietf-opsawg-mud-iot-dns-considerations-01
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: Tue, 06 Apr 2021 00:23:32 -0000

tirumal reddy <kondtir@gmail.com> wrote:
    >> I think that your comment misses the point.  It isn't about DNS
    >> filtering, it's about the MUD controller getting the same view of DNS
    >> as the device.

    > I don't think it is possible for the MUD manager to get the same
    > responses to DNS queries as the IoT device even if both of them use the
    > same DNS recursive server (e.g., successive DNS queries may never
    > resolve to the same IP address).

So, short of deploying SOCKS5 for all IoT devices, what should we do?

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

v2.23.0 | Report a Bug | By Email