Re: [DNSOP] extension of DoH to authoritative servers

David Conrad <drc@virtualized.org> Wed, 13 February 2019 16:30 UTC

Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 065BF124BAA for <dnsop@ietfa.amsl.com>; Wed, 13 Feb 2019 08:30:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=virtualized-org.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 3TzJ0FcMvLYh for <dnsop@ietfa.amsl.com>; Wed, 13 Feb 2019 08:30:17 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 B58001271FF for <dnsop@ietf.org>; Wed, 13 Feb 2019 08:30:16 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id n74so1364794pfi.9 for <dnsop@ietf.org>; Wed, 13 Feb 2019 08:30:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized-org.20150623.gappssmtp.com; s=20150623; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=kr/cLto6CAh48FyXCx4fyxZxVRvOQo4f3Vaju1r95Js=; b=toi2h4HjMbXvzHJTFoIpGQUvgBgKuJbTZguXcOvQzk9RqhcMLcmj1U6v85y9bGaQWi oFAj4+jOFgLxET1WcFLwc/hTZhFmjJ+mpKkKTC5/No4OUymys/nWoSzqDZ22KG53lffU OU7nCMYqr9qzslKOI9ZzEBETaJPloexUVZs//nyKc2is5BKoJlLIcuCvWJLhzNWfyfW+ +EexgRo1VolQMp743Z2+P79KnDdyCfXJjTkwmc1iMhA1g05p+PXxkxna8KHbFOQFoUrl iLeX2D81zIop+u6E7k4O/Ljv8QGuQxOGyvCH/nFUujH1TakA6Z1rH/3yWZHM2GrfPg9L us9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=kr/cLto6CAh48FyXCx4fyxZxVRvOQo4f3Vaju1r95Js=; b=MHpS9w5iSCQZoqjCKNFlj++rNSfrOWppntyU9jAmVpzFGElzAScoWKd/SjPZjZgdUd PLeSmCJrqJNArYkQ4Cs/EnYAjasoGIkncjAZBdzV7RKdDrQOBAcGVgx1Lo2xmTA7K0Bd hoqcaJsV4D+MOgWTTtBswmrM25NYkgqAVie5gGxiAP4GYSfr5BaX3+NPnSdy+TdUHqLK Rzu7cHyPeq/VgJDOyFqbJAvFVl8L6ZrlPTCDN80ssJpZNhnkpNTVNISueZx0UPWYq1Yh cxOqG8LaJm9bR/Lk3viDkEhcYdKtQ1KC2ia3PpDKMFICARucSq/4L2r+UvSNzgwIeJe7 EySg==
X-Gm-Message-State: AHQUAub4AmL0HU4tUs6Js10cePxSDjgN3nI5uJHxOKbJhR+Jkp3pJ2er wlwjWVwnq8ng8vLvsoFO0chyRA==
X-Google-Smtp-Source: AHgI3IafV5YYNfsMXPce4GqSQmEWLo70MqA3tdbyK/jZQhv1JRXC4dJsRDkD4gRZzBbJoMWzQS8qlw==
X-Received: by 2002:a63:698a:: with SMTP id e132mr1232369pgc.136.1550075416183; Wed, 13 Feb 2019 08:30:16 -0800 (PST)
Received: from ?IPv6:2600:380:b478:5fb7:a534:bd57:8409:e522? ([2600:380:b478:5fb7:a534:bd57:8409:e522]) by smtp.gmail.com with ESMTPSA id e128sm24724532pfe.67.2019.02.13.08.30.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 08:30:15 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Content-Type: multipart/signed; boundary="Apple-Mail=_66CD7318-68B3-4F46-83CD-5078BDB8BAB2"; protocol="application/pgp-signature"; micalg=pgp-sha512
From: David Conrad <drc@virtualized.org>
X-Priority: 3
In-Reply-To: <201902131403257357123@cnnic.cn>
Date: Wed, 13 Feb 2019 08:30:11 -0800
Cc: dnsop <dnsop@ietf.org>
X-Mailbutler-Message-Id: 6E058640-B665-45E2-B621-B467625F90E2
Message-Id: <0CFDF54E-E57F-4500-8285-96A5EB035E9A@virtualized.org>
References: <2019021215560470371417@cnnic.cn> <alpine.LRH.2.21.1902120846480.18026@bofh.nohats.ca> <201902131403257357123@cnnic.cn>
To: zuopeng@cnnic.cn
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bakNds3G1vxy6AE5-Nd4RqQ1S54>
Subject: Re: [DNSOP] extension of DoH to authoritative servers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 16:30:19 -0000

On Feb 12, 2019, at 10:03 PM, zuopeng@cnnic.cn wrote:
> that's ture. but in my view, if the trust chain is built, we can ensure a resolver(or a cache) is always talking to a identified server and the channel is always secure, then the content could not be tampered.

Your model of how the DNS actually works is too simplistic.

Regards,
-drc