Re: [Add] Unstated assumptions in What to do in this potential working group

"John Levine" <johnl@taugh.com> Thu, 22 August 2019 01:08 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 530DC12010E for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 18:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=egYbvxlD; dkim=pass (1536-bit key) header.d=taugh.com header.b=QGJ7jnTo
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 dYrCcNTyftVf for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 18:08:51 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4C9912004C for <add@ietf.org>; Wed, 21 Aug 2019 18:08:50 -0700 (PDT)
Received: (qmail 94037 invoked from network); 22 Aug 2019 01:08:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=16f53.5d5deb21.k1908; i=printer-iecc.com@submit.iecc.com; bh=3r9NdOofiVGqwkfoGHoYkulTBPC9wCdX4EKmX95p0ec=; b=egYbvxlDiaHN4kIARPCWuR3xaghZcvAKLkkaGo7jFT7p62UGziwMQdrf7/K71+13ULR5OOmkiaEKVA4kUwFn+sF0MIjrnrNko5RjcXecFfvCISYr8b3blOZsG2Q5mKQ55iPQlTRJWiv5n0vD/LPqxKnhASQweCgZBjAT574Po4DikIuM+zXg5hlaqTHW05E0SSvmYR/7W/A5kw3Ya3xBp/LeXwlIorFJPFyADPV/WK+G0GqhNZ0guwJWf8dfQP/Z
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=16f53.5d5deb21.k1908; olt=printer-iecc.com@submit.iecc.com; bh=3r9NdOofiVGqwkfoGHoYkulTBPC9wCdX4EKmX95p0ec=; b=QGJ7jnToyFD1KKyELmK47thG8Hcb/Pw67tbPzRL2ci5tVJzCytwhod6m7/5BJRNVCDrqbcd9A2X/KhvQJ3H1jUamypVws9HMX/nmtgwUe+26IOdZZR3HMUlDnorjr7f47egSUAQXArctBWtEG3n64T9Ux9hgilGnc5lL3KWqBCIvMskAN5bao+x5U0ZKwFhfaXI5RAD0CQ+4suhoyLl5C+WhzaKVCW8moa2xJgRyojXFPEViIYsfgmvHHfyRNHon
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP; 22 Aug 2019 01:08:49 -0000
Received: by ary.qy (Postfix, from userid 501) id 0010F89BB7F; Wed, 21 Aug 2019 21:08:48 -0400 (EDT)
Date: Wed, 21 Aug 2019 21:08:48 -0400
Message-Id: <20190822010849.0010F89BB7F@ary.qy>
From: John Levine <johnl@taugh.com>
To: add@ietf.org
Cc: vittorio.bertola@open-xchange.com
In-Reply-To: <1081276693.4678.1566384230225@appsuite-gw1.open-xchange.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/adVWxjmofcsEBu4O0fgr00WQ8tM>
Subject: Re: [Add] Unstated assumptions in What to do in this potential working group
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2019 01:08:52 -0000

In article <1081276693.4678.1566384230225@appsuite-gw1.open-xchange.com> you write:
>I still think that having an agreed write-up of the issues and/or of the use cases, even without any recommendation on how to deal with them, could also be useful. This was the main
>subject of the original three drafts presented in Prague.

Agreed.  We're still seeing people argue with unstated assumptions that are obviously not the same.

For example, a bunch of messages have gone by that clearly assume that
the person using a device has chosen to use a particular DoH service.
I can easily believe that could be the case for the very atypical
bunch of people in this discussion, but not for grandma using whatever
defaults her browser or phone app or ISP or malware set, nor for IoT
devices that use whatever.

I see similar cross assumptions in "trustworthy result."  Some people
apparently assume it's synonymous with DNSSEC validated, but for me if
it's a bot trying to find its C&C host, the trustworthy result is
NXDOMAIN or SERVFAIL.

I think it would be useful to try and tease these out so we at least
have a chance of agreeing on what we disagree about.

R's,
John