Re: [Driu] How to describe various flavors of DNS resolvers

Erik Kline <ek@google.com> Tue, 15 May 2018 04:46 UTC

Return-Path: <ek@google.com>
X-Original-To: driu@ietfa.amsl.com
Delivered-To: driu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 416D9129C51 for <driu@ietfa.amsl.com>; Mon, 14 May 2018 21:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.511
X-Spam-Level:
X-Spam-Status: No, score=-17.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 iyVkOD607Sc0 for <driu@ietfa.amsl.com>; Mon, 14 May 2018 21:46:27 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (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 1951D12EAC8 for <driu@ietf.org>; Mon, 14 May 2018 21:46:27 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id p4-v6so14474884wrh.3 for <driu@ietf.org>; Mon, 14 May 2018 21:46:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EaAHRh9oIj43g+1EPxCkiVUuqKsbAmX8j/lEZRAVdLc=; b=h9YqbiBlvBHwkAU+fVWeAY4YEwcdXS0oUZ44vSNpUlw9siqLgviezoLsFH0kz1OHmh ks5eOnThTqmgfZeFBd3PuV7Y6PMqJPRtY3kIulsQ1NMycYjUba9T2WlVT+5ZqDT+I0ZC 0Kik3+GZ4L9mMkFBkevf3eXZ0Jeja0Bw7SkVS/d3jFYZ62k9Nj0459y0q5LfYKnETLBA QfUvNFGY+8Zmm9TtxHuHQXZECIbXDgxuvfgbayCldmM7tm2DFh7eKd1T6kASGIZdgLHk xMiiVzsWFIE9YLbxd8+3FTgsrPwGVMJbyWIz6soHfqwVI7Wpt0DeKZCtTxfEgEmhQ6jg FWHw==
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=EaAHRh9oIj43g+1EPxCkiVUuqKsbAmX8j/lEZRAVdLc=; b=mkYEp2qtQyIUCR6jlHKnyomESmlGVYGMoN98EqtGXHcfWEZRHVEeZ/wTYJqwoF4zx8 lhSQQG3HwFysBqOmkEf/m6+IpE/8e0Yn9vdJNctCw68tv0j0q9Aw08TnxW/kz/wq3EMZ pu37Be7VIzaE9/I825tVRkTtnk4YGXX4o1KnPUivmADkWCHNoaKAO5iNaM0RwaR+pHuD R9QJSgmQSW2OZr4FWCLmS4WSbYORjDgCbC6AtxQinVvrvPVCv1rdDLoBf25lcYQqqnpx SwyxIXGhXog3QMhdMUg9uUvMAyKmYUPlkwOs4WKXsXg1phkQRkoIYnD5ElyHFa/o2mpP 5IPA==
X-Gm-Message-State: ALKqPwewpO+SYW6gHpZJgfNHOH9G6+iAB3ZaNYcU2RfnooKF6MvT2l/q LTVZbgsCEJc9YYGdnZXIBOhQ7bJo69oHudgw+dCDIm8d
X-Google-Smtp-Source: AB8JxZrzDDKnEy/m0+96OobOZyI5Fpc0qKl3aelG5BcJa92d8z0HYMTW+jbTFvPycYfxf3UFmR2Gfy2YqG6uL+T/ENg=
X-Received: by 2002:adf:9544:: with SMTP id 62-v6mr8463988wrs.74.1526359585271; Mon, 14 May 2018 21:46:25 -0700 (PDT)
MIME-Version: 1.0
References: <50A2740C-98AE-4EA9-A290-B3231FFCBD0D@icann.org>
In-Reply-To: <50A2740C-98AE-4EA9-A290-B3231FFCBD0D@icann.org>
From: Erik Kline <ek@google.com>
Date: Tue, 15 May 2018 13:46:11 +0900
Message-ID: <CAAedzxqkvPan_bGLQAPnViS6_59eNB2Hu4Ex+ZEYL89Qh7Mc_A@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: driu@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="000000000000e92ab1056c37483e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/driu/uFnHpi32z5e32eDtvAP2Y5cX3a4>
Subject: Re: [Driu] How to describe various flavors of DNS resolvers
X-BeenThere: driu@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "DNS Resolver Identification and Use \(DRIU\)." <driu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/driu>, <mailto:driu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/driu/>
List-Post: <mailto:driu@ietf.org>
List-Help: <mailto:driu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/driu>, <mailto:driu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2018 04:46:29 -0000

> Greetings. This mailing list has many purposes, but a (hopefully easy)
one is: how should DNS-over-TLS be described in protocols like DHCP? Should
there be a separate DHCP option for naming DNS-over-TLS servers to the DHCP
client? If not, how should clients upgrade from DNS-over-53 to DNS-over-TLS?

I'm not sure I understand the benefit of trying to provide this extra
information.  I think clients will need to probe nameservers for their
capabilities.

Do we think TLS-only nameservers are a likely operational model?