Re: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)

Ted Lemon <mellon@fugue.com> Thu, 14 June 2018 19:46 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E575A130E8A for <doh@ietfa.amsl.com>; Thu, 14 Jun 2018 12:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 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_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 rJc25aOtdRtF for <doh@ietfa.amsl.com>; Thu, 14 Jun 2018 12:46:15 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 29794130E79 for <doh@ietf.org>; Thu, 14 Jun 2018 12:46:15 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id t5-v6so8390217ioa.8 for <doh@ietf.org>; Thu, 14 Jun 2018 12:46:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zru4mlWH5+TD0JbwZwuftQhBOWuq8GFHh5Vh687g/2Y=; b=XE0An00SXjxDg6iNaX+Yoq4cIDyLTKdPjA2HhAVSbGqzOYAWxqBnPqUdP8JlnAhS8f X6BOIlKsCALh8iNBCk8i8xRKJ/SETBAuUjR/FzIJ+4yWEEFveuwS+wr/7r93prWiMpme i7knV8I3p0C8EPImuzG9A+JRh3kICojEZPg6gSjXa6mSbRXo03EI6CEDYd4wysRIBWRs VtiVI5X4gAu+mQ5gD2bLcymAxwVbiLeSnRJyPzkdHbZLa1hXR4xQSNHzzO2GzRdXoglb p3zzJrlyWCu3otc491JUXhb3FTxGDJJ5zwsmyw2tjOgL2fWtXin/Tmd8/+9aD3cf/IiH XG6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zru4mlWH5+TD0JbwZwuftQhBOWuq8GFHh5Vh687g/2Y=; b=Teb9UtEoouSzG6q7Q0GruDEHEUiRCJwjE/lzHRz69wF7UC3NHFpGBf+QKZSt+449vH CZEXwLFrJu/1olY5Q95EnNavbrRW6VZo9davkZjDyIBPf39Ftr3HgaUGOtOQdxdY2cvc Mkwl0Kk1CRSUWZst2jVjeOQDCESmemEKuI9D60L9bxFcGY12lxNAVZtfL6lJeIHENxE5 3KiJpmdcg70Unn1KaVB/wbBNc++oXPz9UcJ3PuK2qtLT3b3CuvmA/VN8ipoMCxYGsDZw ZQI7CdsEftW4nZB6iBudjb1B5Ipa7klg6ZU9NxZDlpAkqAa9JErES0JBD67Pk8LUa1Lz q62A==
X-Gm-Message-State: APt69E1jXQTKZw55y7sqfUx7wD+r00J5YrOu7pZPYvHu8P4WuUkZJSMq /8x9WTYFSnD1L+9ynsXVHhpcOFP+WlOccE47GZB0DA==
X-Google-Smtp-Source: ADUXVKLuy+clI1JMK7RodHyJfiHy/RoM/FrfywhEl2rx5REKSrNqE7u5B4PmjjeVWBsbVwoiRGGSZC5JySd5csvYU3M=
X-Received: by 2002:a6b:be05:: with SMTP id o5-v6mr1423531iof.45.1529005574508; Thu, 14 Jun 2018 12:46:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:6f86:0:0:0:0:0 with HTTP; Thu, 14 Jun 2018 12:45:33 -0700 (PDT)
In-Reply-To: <602C852F-D988-4D3C-A959-E7A6EAE6AC3E@icann.org>
References: <1E183D79-5716-47E5-8604-A4F5DC7588C2@icann.org> <045241e6-6d9f-162c-6ae3-0b10d59d21de@bellis.me.uk> <6BB0D47F-2BA3-4D9A-A125-1D1E180B06E0@icann.org> <53c320bc-6ea0-21f4-c7a1-1da34bbdb38d@nic.cz> <CAHbrMsBoKE-pfz97ZDb9ReLKMedk2KJ7xLCw_MPmxVtqF7PcuA@mail.gmail.com> <20180613192030.GA2792@jurassic> <CAHbrMsACdaz13v=2jbpZq1RU-_CP36Cgz13iFFWVj8qrjQ0b=g@mail.gmail.com> <20180613205637.GA23215@jurassic> <CAOdDvNr0ob_zhMw1BT_h8n77ecx5vht8WJ7OiwwDPrj0Wxf8SA@mail.gmail.com> <20180614042217.GA25915@jurassic> <20180614044113.GA27115@jurassic> <alpine.DEB.2.20.1806140728270.30130@tvnag.unkk.fr> <74D48781-9F05-482C-ACB2-7AB027611489@sinodun.com> <40ac87db-dfdb-5305-338d-ff3afb8e159d@o2.pl> <F6CEE7B0-E0BF-4EF7-9BDD-4DA7B539A511@icann.org> <CAPt1N1kBEv-ACPiWKckMGrQFu=F=pTD-D6oByzktmQe76AZYZg@mail.gmail.com> <602C852F-D988-4D3C-A959-E7A6EAE6AC3E@icann.org>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 14 Jun 2018 12:45:33 -0700
Message-ID: <CAPt1N1=uCAGJ26KjVj0LA70-p91fWQD-jj+8c+t=M20tuSp_Nw@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: DoH WG <doh@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000211138056e9f5a82"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/397o79UWRq2qyU-yHKnjzx9gPXs>
Subject: Re: [Doh] [Ext] Are we missing an architecture? (was Re: DNS Camel thoughts: TC and message size)
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2018 19:46:17 -0000

Okay.   But do you *get* protected DNS if you discover a DoH server using
DHCP?   What does "protected" mean in this context?

On Thu, Jun 14, 2018 at 12:39 PM, Paul Hoffman <paul.hoffman@icann.org>;
wrote:

> On Jun 14, 2018, at 12:34 PM, Ted Lemon <mellon@fugue.com>; wrote:
> > Paul, Mateusz, can you talk about the use case for using DHCP to
> discover DoH?   It's not at all clear to me.
>
> An OS might want to offer protected DNS for its stub resolver.
> DNS-over-TLS is one obvious option, DOH might be another.
>
> --Paul Hoffman