Re: [DNSOP] [Ext] Re: New draft for helping browsers use the DoH server associated with a resolver

Shumon Huque <shuque@gmail.com> Fri, 24 August 2018 16:36 UTC

Return-Path: <shuque@gmail.com>
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 319C5130E10 for <dnsop@ietfa.amsl.com>; Fri, 24 Aug 2018 09:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NlMXLHIwVBTb for <dnsop@ietfa.amsl.com>; Fri, 24 Aug 2018 09:36:19 -0700 (PDT)
Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (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 8D96A12F1AB for <dnsop@ietf.org>; Fri, 24 Aug 2018 09:36:19 -0700 (PDT)
Received: by mail-yb0-x233.google.com with SMTP id z3-v6so3689515ybm.8 for <dnsop@ietf.org>; Fri, 24 Aug 2018 09:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eLvhuBMByFTP54XbcNoQ7S/WM2do0JWouwLxFGvhDYk=; b=qs5XGx+BjC7WzPwuyxyA14FOzpIBFR56ha73j+YinV7KfSJ+UrH8qlwXMstpCwwxps W+pnaJsrl4QN4rTl5NIQQW6qOHs/8t0aPL9eOyxVtSMpuw+vbZ6g3E2d9Iy2aUlab1t1 JeBayZnGCw2S1pUlYjRqk+IBYkDrdQIYMWWCt1yixEWa2WAoAkUV4STxVTax4RnFKkvn pO+9xaQRpOSzrMIl94J02m6B94fP/6nDmJhyXd3QHJ/ksXYRqS8OMI4dmOG+50e1ijA9 RoQeW1agv1oPxra8eFGK8nztshIaP0YdHRT6vlG4CBmvb7NUCVtb1VJDxMGPoQdweOMV stRw==
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=eLvhuBMByFTP54XbcNoQ7S/WM2do0JWouwLxFGvhDYk=; b=OmIh88X0qPItB5IPEXe9LAJn6X+e1W3wmqlVlh+UYKdAQCcpMrUiqakaqTHVDik95V +2HOjmg/5cpt5HQy8Jf2pZtCAh1ccZMwpERa3WcwGIzS+LlKSt7s+Jz26KdiBeJGNQkQ HWW08zYtOdRu2RPfjrKY7I++wIHNlZZSbaZEFKK1leNR7jR59M3AxFG9DUUEwjutBiTQ ReTqAciHUZCr5PVs1LUhhncc2VYIY+ILluo/0/+mFiDamjCmG3IYYxxczzV11EHE/3Pl 9FMVDFom/p8CxXva7ue1ONJZmerGRe1mQAC8yEq65W4g54cu5v2k/fdgKM3IRdGbG7CE n0Lg==
X-Gm-Message-State: APzg51Ao+x73cewVZLFyaJbRRxqaow50idtkT4PR7mgRHP/I8dbUaJnR DPDwIHZE3yTbSwR3WnMdny5cBlYl/35qT7kzV2w=
X-Google-Smtp-Source: ANB0VdanlwtBqNcLl8tWvvifqwei8YZJs8N8CjYgP8GYxi/LFEP6g9cnJ47rE/FWxoRHkmzzVUhYYWykim13v06rMiA=
X-Received: by 2002:a25:4557:: with SMTP id s84-v6mr1509406yba.43.1535128578517; Fri, 24 Aug 2018 09:36:18 -0700 (PDT)
MIME-Version: 1.0
References: <3D4A9165-6EE8-4997-A9F7-DB19632C25F3@icann.org> <5220d889-e587-d6dc-db45-0d76370eabae@nic.cz> <61FF26F6-F2E2-48C8-A4B6-94FC6652D55E@icann.org>
In-Reply-To: <61FF26F6-F2E2-48C8-A4B6-94FC6652D55E@icann.org>
From: Shumon Huque <shuque@gmail.com>
Date: Fri, 24 Aug 2018 12:36:07 -0400
Message-ID: <CAHPuVdU7T0n_PNyGb7SzS7oAa35uDDe3cse9kQpxQZrWJzU_Ug@mail.gmail.com>
To: paul.hoffman@icann.org
Cc: vladimir.cunat+ietf@nic.cz, "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b6f1f057430f96e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DYqF5DCuHu6xfejNchKOoTXVDFg>
Subject: Re: [DNSOP] [Ext] Re: New draft for helping browsers use the DoH server associated with a resolver
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 24 Aug 2018 16:36:21 -0000

On Fri, Aug 24, 2018 at 10:26 AM Paul Hoffman <paul.hoffman@icann.org>;
wrote:

> On Aug 24, 2018, at 6:43 AM, Vladimír Čunát <vladimir.cunat+ietf@nic.cz>;
> wrote:
> >
> > On 08/24/2018 02:01 AM, Paul Hoffman wrote:
> >> Thoughts?
> >
> > Well, if the OS resolver is validating, it will SERVFAIL with such a
> > query.
>
> The protocol requires special handling of those specific queries, so a
> resolver that understands the protocol will give the desired answer. A
> resolver that doesn't understand the answer will give NXDOMAIN even if it
> is validating because that RRtype is not in the root zone.
>

(Haven't read the draft yet, but a quick comment on this point ..)

Surely you mean NODATA (NOERROR + empty ANSWER section), since the root
domain name exists. If validating, it would additionally provide the signed
NSEC/NSEC3 record at the root disproving the existence of the RRtype.

Shumon