Re: [Add] fixing coffee shop brokenness with DoH

Eric Rescorla <ekr@rtfm.com> Wed, 24 July 2019 17:15 UTC

Return-Path: <ekr@rtfm.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 2334A12015B for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 10:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 7GHIeu7fs5xn for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 10:15:06 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4573120112 for <add@ietf.org>; Wed, 24 Jul 2019 10:15:05 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id v85so32454319lfa.6 for <add@ietf.org>; Wed, 24 Jul 2019 10:15:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RwaEFKHhtZfVyP7U9PO0pWJSqWIYi8SxRRSKy37gnfk=; b=sVZ/jC8tTxcxl2XaFNyV3E2RjirhIbx+6Msg8wI7U8e50q7Cknf4DK/rDJtT+91XzU PS/Bt9XHPzg5wvZwKBZQx2xmqlsTi47c4LdeGHzLCFxeRBWok9AjOh0jzBj8veN7mTsO ptggi3FDLoP50zl92GmzhlxCxBdTltmc/pdbgU3PuEJwfklwk+KPqhQ/I1o+xY/4WPBW 3BvLD44+0m4iDyqKIG5VyAPr7W1676pMLZcG27/bLxCBOhbsWzU8PBDb3oRoC+rnezIX qaagzc8GCEP1tnq4RFSYdrpKhooCHEFpRaT47lQ/TBmTC4fDyuGm5xagho6CXrTBAuXO CUCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RwaEFKHhtZfVyP7U9PO0pWJSqWIYi8SxRRSKy37gnfk=; b=fxalgA2hk77du10nVmPnXxm7Yxf51qPcZuN+kWDQRjPv0eC6ALW5pDG5CXasWEB7Rq qeFK8pLTz2qzxq+YGWwv9yQjxVwqWHEdx0Lkjlim9EySU2Wjz88s5ES86aOEHWHq3Noa XpwbYQinrP4EZB3D7++ThrI16tbeRpe5CDhj5feeHZj+K2Ye9vSWPaXxrS5WfoWT0o0t Bsx0PHJ/0k3DQ1pKBCeMQggBE04DOTBYN2R31SsVz51lX/XQGIlBQdcv3xextG4E4oYA bKe95L0KbYauAYz/CC4n+lZfZrnDuzGbxpnA7hNMlVmVo7IvglKz1+eJ/xz8sVxtgl1+ 61OA==
X-Gm-Message-State: APjAAAX66Z3LPY0E1ZgmEMsOQpzfXIdbLK0rWOzp4NE2FTIJB5Zn5s85 KqwQiqGG4v13BtuxFSOHBo74VRnXZ/kR6B6YMzkBQA==
X-Google-Smtp-Source: APXvYqxVDV5ZMZfhQ7vVJCJUV/PZp7xobo2I1h/ONpwLgSgd0A+nfTEdU9fTNiKGHrH9se8PumQo3SyZoFXy7Z4elnQ=
X-Received: by 2002:ac2:51a3:: with SMTP id f3mr11063209lfk.94.1563988503853; Wed, 24 Jul 2019 10:15:03 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <2D09D61DDFA73D4C884805CC7865E6114E23910C@GAALPA1MSGUSRBF.ITServices.sbc.com> <14DF8769-A817-4C06-9140-80198518244F@akamai.com> <CAChr6SzH1EycAr5n+dK5BQcG=0Zsw66qE=8Rptvq7SEoEvQQ=Q@mail.gmail.com> <E5A0DAE2-A718-41EA-B490-58ABD0F31CF2@rfc1035.com> <CABcZeBMqvZivS_Hk_2mSOAOnM+mHy1mtcwnHVFc14v_jdkgU=Q@mail.gmail.com> <1EFB37A3-23C6-44FF-B001-8F04B381EC04@rfc1035.com> <CABcZeBPB2Bb8RCigDt+tJ5Lz3KQQnPAVVkrF+fDUiTFJcw=eVw@mail.gmail.com> <D3359CC8-80B4-4443-B3B1-F2AD80C94DA6@rfc1035.com>
In-Reply-To: <D3359CC8-80B4-4443-B3B1-F2AD80C94DA6@rfc1035.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 24 Jul 2019 10:14:27 -0700
Message-ID: <CABcZeBOZiu_=VfWJDY_9V86TiGpsuZRKMCiersopxD+kTBBUtA@mail.gmail.com>
To: Jim Reid <jim@rfc1035.com>
Cc: "add@ietf.org" <add@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000348f7d058e707328"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/qbmXIEbrlEnq9OcRoTVHBqDtxLc>
Subject: Re: [Add] fixing coffee shop brokenness with DoH
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: Wed, 24 Jul 2019 17:15:08 -0000

On Wed, Jul 24, 2019 at 9:00 AM Jim Reid <jim@rfc1035.com> wrote:

>
>
> > On 24 Jul 2019, at 16:11, Eric Rescorla <ekr@rtfm.com> wrote:
> >
> > See my response to Ted. From the perspective of the client, acting
> accordingly looks basically identical to how you behave with a valid
> NXDOMAIN, and so DNSSEC doesn't change the situation very much.
>
> Not really. A validation failure is a fairly strong indication that the
> resolver is lying to you.


Not really, no. Our current belief is that there is going to be quite a
high rate of non-malicious validation failures.


Or should be. So a security-aware application would know the current
> resolver can't be trusted (or is at the very least suspcious) and take
> suitable countermeasures. That's what I meant by "act accordingly".
>

What do you believe those countermeasures are?

-Ekr