IETF Logo Mail Archive

Re: [OPSAWG] [Mud] changes to draft-richardson-opsawg-mud-iot-dns-considerations-03.txt

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 26 September 2020 23:02 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 4B98E3A0BDF; Sat, 26 Sep 2020 16:02:55 -0700 (PDT)
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 GEOy1mkSCJHD; Sat, 26 Sep 2020 16:02:53 -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 EB80C3A0A26; Sat, 26 Sep 2020 16:02:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4148A389A2; Sat, 26 Sep 2020 18:41:22 -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 qWv1eZYbd7H2; Sat, 26 Sep 2020 18:41:12 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id F17AD3899E; Sat, 26 Sep 2020 18:41:11 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BCC7075; Sat, 26 Sep 2020 19:02:37 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tirumal reddy <kondtir@gmail.com>, opsawg <opsawg@ietf.org>, mud@ietf.org, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
In-Reply-To: <CAFpG3gc-PoAdvCB5p201-uZrMsdi4Cr1hR_YM-z2bgD9tvZVUw@mail.gmail.com>
References: <160082461431.2339.6222888407127336620@ietfa.amsl.com> <15779.1600960819@localhost> <BCB5CBD9-78C0-471A-8C32-88E4FD406136@cisco.com> <CAFpG3gdMxw2QGUFhWQELYT8oaMgVuvc5_hQf_Pfk3T3vwc2rmA@mail.gmail.com> <15491.1601055706@localhost> <CAFpG3gc-PoAdvCB5p201-uZrMsdi4Cr1hR_YM-z2bgD9tvZVUw@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: Sat, 26 Sep 2020 19:02:37 -0400
Message-ID: <27239.1601161357@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/rKwW2_kdVkY0MwYEk1u03pHwPJ8>
Subject: Re: [OPSAWG] [Mud] changes to draft-richardson-opsawg-mud-iot-dns-considerations-03.txt
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: Sat, 26 Sep 2020 23:02:55 -0000

tirumal reddy <kondtir@gmail.com> wrote:
    >> tirumal reddy <kondtir@gmail.com> wrote:
    >> > +1.  The problem is not just with public resolvers but also with
    >> > designated resolvers. The IoT device supporting MUD must use the
    >> > encrypted DNS server discovered in the attached network.
    >>
    >> Yes-ish.
    >>
    >> I don't think that we have to mandate use of encrypted DNS servers,
    >> as long as it's the ones on the attached network.
    >>

    > In the home network use case, if the CPE does not support an encrypted DNS
    > forwarder, endpoint will discover and use the ISP encrypted DNS recursive
    > server. The CPE will no longer be able to enforce MUD rules. For instance,
    > Firefox can discover and use Comcast Encrypted DNS recursive server, see
    > https://tools.ietf.org/id/draft-rescorla-doh-cdisco-00.html.

It's reasonable that Firefox might do that, but I don't see why IoT devices
should follow suit, and that's the point of this document.

Except in some very niche digital signage and kiosk use, I don't think a MUD
file would be appropriate for a general-purpose browser.

--
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