Re: [Doh] Associating a DoH server with a resolver

Martin Thomson <martin.thomson@gmail.com> Wed, 24 October 2018 01:10 UTC

Return-Path: <martin.thomson@gmail.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 5A6B412D4EA for <doh@ietfa.amsl.com>; Tue, 23 Oct 2018 18:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 G3YytgqlIB_l for <doh@ietfa.amsl.com>; Tue, 23 Oct 2018 18:10:40 -0700 (PDT)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 C6DDF128CE4 for <doh@ietf.org>; Tue, 23 Oct 2018 18:10:40 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id c32so3354510otb.8 for <doh@ietf.org>; Tue, 23 Oct 2018 18:10:40 -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=J/yB21EMW45jl7LTiP002CnbI27/hrQ3Jgp5DamDGjc=; b=s+iM0atnpiJ5VTGTkXb68IhW2RrNQ2JO8Yww/ffUxXuxBWB8n+S8eJQmLn3SXdyTY4 MEol0WN9jHycCXsS6grjOXG2uDdzYYMdDKHnEI3a2zrUfbtq3Pohgo4qI9ikuLKUz71Y bYVz9lxKfOZ9rLj8KL44vVGVjQBtb6z7Sq7qDzNP47+mrx345uNou4pmrqsQh3Fa3qWX apMW0/UYOzixqWHldd0dEGuBQ+hB5cALrOnYiO49JYFH0tEzqiclEPk84ZQMH0s4hGdK CKjHOA6xEfJdtzB3cRWSkn2w0x/ODpYiL9vHrHGm2CbqLvU1on2/jBVRgPWLLfX42rAW jtTg==
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=J/yB21EMW45jl7LTiP002CnbI27/hrQ3Jgp5DamDGjc=; b=OL8y3uTdIi5qxR4Mj6P2EKef0uOJ117juq7mnzgAW2yj/9OPwsQnPqtCVNZ5PdCGms g6PZa71YhlEASRxX5kTlrXJj3sJjrv2mM1jAbJ/ZMP8iH1asC9dEeqRkJwl6PFNtDCzL bog6T4bzcEM8BSQoiUTwdfDwpW1FT77xobix9hKInpVuhS1WtZaYI0oiPqw+kfPDhz0M gWsCEssU713d/RAI2mpERWRG1vk2eXVgqf9Xh+Ru3F/COF5+rXIfWmATwwkasPDuOnTv /9/D3B2eDvBu+5SNpZ49X7nTGeRM2m94PINkYWhy13d3+IFvgtuQmTNDwl5wNwyhpkAv FzKg==
X-Gm-Message-State: AGRZ1gKuLn5xxI6/c20zr9vaIUpPO+u8/yZ3CfYDLljJmcMvecv55SwL Jy1M6GnwoUrOsczIUeT8IrVcYJqRcNku7t9wMJdj4wpDbmo=
X-Google-Smtp-Source: AJdET5cX2QjErjMiynxIGTGKOvOX8/Es4E/PaUdjiqeRisKUCEb+NzejJQv1oyNoz0K0QQwk8pAC/vEBi1Qzc+em+h8=
X-Received: by 2002:a9d:7602:: with SMTP id k2mr357261otl.299.1540343440096; Tue, 23 Oct 2018 18:10:40 -0700 (PDT)
MIME-Version: 1.0
References: <02C39DFD-9550-447D-B00E-702B441A88BE@icann.org> <CABkgnnV2YMtcdOyMfE2NMH4L1ZbK4dcp1KQt3FttCfz-nfQd6A@mail.gmail.com>
In-Reply-To: <CABkgnnV2YMtcdOyMfE2NMH4L1ZbK4dcp1KQt3FttCfz-nfQd6A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 24 Oct 2018 12:10:31 +1100
Message-ID: <CABkgnnVnyCg==75P2A_kLgtTGq2Wwdkw-930o1YEMT53PhpqCA@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: DoH WG <doh@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/2LlY0QqTbo7yajrxaWvSkTnCV5M>
Subject: Re: [Doh] Associating a DoH server with a resolver
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 24 Oct 2018 01:10:42 -0000

On Wed, Oct 24, 2018 at 12:08 PM Martin Thomson
<martin.thomson@gmail.com> wrote:
> Why do the IP-based spelunking?  It requires that the resolver (which
> might not be a DoH server) do HTTP as well.  Can't you define a record
> that could be placed at the resolver-addresses.arpa name?  I hesitate
> to say TXT, but I can't think of a good reason not to use that in this
> case.  Multiple such records could identify different DNS-over-foo
> variants.

Oh, I forgot.  IP-based certificates complicate things considerably,
and will make this impossible to deploy in many cases (think of the
many resolvers with 1918 addresses, for example).