Re: [dns-privacy] ADoT signalling

Eric Rescorla <ekr@rtfm.com> Mon, 04 November 2019 16:17 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 372DB1200EF for <dns-privacy@ietfa.amsl.com>; Mon, 4 Nov 2019 08:17:43 -0800 (PST)
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 y-MpXUE9EZji for <dns-privacy@ietfa.amsl.com>; Mon, 4 Nov 2019 08:17:41 -0800 (PST)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 013C2120B40 for <dns-privacy@ietf.org>; Mon, 4 Nov 2019 08:17:41 -0800 (PST)
Received: by mail-lf1-x12d.google.com with SMTP id f4so12684560lfk.7 for <dns-privacy@ietf.org>; Mon, 04 Nov 2019 08:17:40 -0800 (PST)
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=mIaUSkvqBNlgCUSMf1jmEl2vUoNcg+dAQ+PDT5GeWEY=; b=J5mNxnrjssotRFd43yK8VnCrQBlIYpggjgSGm1jh4uWYKPxYfCB6FfwNAQsIay3SM6 iInymU2MNEnNnnu7lEIxq2edum8CASocl66V+WwuD0kygFL9+S4c9oupqW2Bya1FTCu3 vUSm5WBr0QiFHM3XnXvJWmfpiR4Rzh1c8Nqh78wYN6hltluJq5P/TjrtzW8rOYUd/pf3 6lNP2KLVI4fTmA0K1AZMpK2gZhbxNUR1pXKSPGcH2xs6T5tgfETDnNnKUB41v/oIJojU MZ3/Z/3a0ImE35DO7p/eFJsE5RT8Z9jGfFu15b6zvCaos/agZ2cSGBPDATp8sZMRDOWw WtSg==
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=mIaUSkvqBNlgCUSMf1jmEl2vUoNcg+dAQ+PDT5GeWEY=; b=aT3GpWUfoIqF3BSPufAGDmr7NbcraXbpNSqMRFAq8htdryAR6mxaBdvncCG6C/mtTK WoDJHKxgAjv8EBATnGjFJVdBpY5pZ3qTBiNILy+M9Ehgrz6jNH/Tz47GFmxhRPrjsnGI h0dq/LhRo69O0hQo6FiJfOGX1zNtFjqYk61uhmwvpn3Js1GHOkv8vCfHxSGR3U2TLwdH eO6KwkjOJqRhgmOUdUvaGyfQVhjZHXpz7cR5Ug7RG/Nip4IqlWtMG3NRAJr7pD6LQGAQ zKsa1tqZbXfOMA3KlCoeLUbd1O3mT2gQXx3BEz1PaR2eiUWkRcSYBV+AOVrg9g/3aWk2 VObA==
X-Gm-Message-State: APjAAAXXjyWHW1N7AF5jjq4saY+kP4rmzm+jQ2vSAhV68N6ktMVGp2ZW L10A8PXCjR5cY0a9Usk7VA6FF2rS/L0twdKpnVMqzw==
X-Google-Smtp-Source: APXvYqyA3BcibFX9TqAUuEr3UhLrvDiK2jlSy4NQxwKDbnw81DzBXOXRKSDp+rx6QDuDKhMQncge9Dqz9M9t3zRJZIE=
X-Received: by 2002:a19:8196:: with SMTP id c144mr16874563lfd.129.1572884259116; Mon, 04 Nov 2019 08:17:39 -0800 (PST)
MIME-Version: 1.0
References: <20191103223335.4395EE54E62@ary.local> <20191104142555.GA10561@nic.fr> <CABcZeBNDPbNznf8dSA8NdVH4TMVJEGGNjR09k4GTyjXWaEm0ZA@mail.gmail.com> <20191104153226.GA15325@nic.fr>
In-Reply-To: <20191104153226.GA15325@nic.fr>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 04 Nov 2019 08:17:02 -0800
Message-ID: <CABcZeBP+iSBvHKYD8oFpxdYAXCbzOtAFyGYzeb=RHbZW_ujzGQ@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: John Levine <johnl@taugh.com>, dns-privacy@ietf.org
Content-Type: multipart/alternative; boundary="00000000000089b019059687a793"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/oHfy-5j6RPgSm8aMNCiQ0HcRw2o>
Subject: Re: [dns-privacy] ADoT signalling
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 16:17:43 -0000

On Mon, Nov 4, 2019 at 7:32 AM Stephane Bortzmeyer <bortzmeyer@nic.fr>
wrote:

> On Mon, Nov 04, 2019 at 07:12:46AM -0800,
>  Eric Rescorla <ekr@rtfm.com> wrote
>  a message of 96 lines which said:
>
> > I'm less worried about the latter because I would expect recursive
> > resolvers to generally be operated by people who are able to
> > establish their port 853 status.
>
> Not all resolvers are big boxes in the central datacenter. I may want
> to run a resolver on a small box at home even if my ISP blocks port
> 853.
>

Yes, I didn't say "control" it, but "establish" it. My point is that you
will generally know which state you are in and not need to do an automatic
fallback.


-Ekr


> > Well, this is why I asked about the threat model. If we care about
> > active attack, then this kind of approach does not work well.
>
> I tend to agree with Stephen Farrell here. If we insist on perfect
> resistance to active attackers, we may never deploy anything. I would
> suggest something more like "probe 853, remember what it was last time
> (to warn the sysadmin about a sudden block), may be allow to whitelist
> auth servers that must have DoT".
>
> For signaling, my personal preference goes to DANE, anyway.
>