Re: [Doh] Seeking input on draft-03

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 08 February 2018 19:57 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 573A5126C25 for <doh@ietfa.amsl.com>; Thu, 8 Feb 2018 11:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 258fHBqqQ955 for <doh@ietfa.amsl.com>; Thu, 8 Feb 2018 11:57:02 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 013351267BB for <doh@ietf.org>; Thu, 8 Feb 2018 11:57:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 86FE4BE39; Thu, 8 Feb 2018 19:56:59 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fe-sxGtMmzJ7; Thu, 8 Feb 2018 19:56:58 +0000 (GMT)
Received: from [10.244.2.138] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5E7ADBDCC; Thu, 8 Feb 2018 19:56:58 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1518119818; bh=FPs9unAiDwrxgqUMzc5dGgvAwAoAMEzOKroThID+cvk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=N3STpI3VDqlNdDfY8a5mg9TBzDahay65B6YS1RrFIok7CxhXTUNxHaOlhSXGd0iyA oHbYoqiB9U5BcxMZoGdYixA8MAl0a0eQS5yei0brMUYL7nCVn5+aGiWoitF78310Cn ajGaFjYiHw3TrcwIWw/wJ9/o2dFKASyfZD8CFmm8=
To: Ben Schwartz <bemasc@google.com>, doh@ietf.org
References: <CAHbrMsDwWvtcZy8fpg9gs3o+gc_umi9okJW6rvv+s4T7K9-sVQ@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Message-ID: <5855fc09-0518-7fb0-56b6-07a8667cbf31@cs.tcd.ie>
Date: Thu, 8 Feb 2018 19:56:57 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAHbrMsDwWvtcZy8fpg9gs3o+gc_umi9okJW6rvv+s4T7K9-sVQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s2mv8zxOBaM9kS7fN5mcKMqchlxEfJBmS"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/xvcFOwGy2o2tVCNDRnuAmhbSGf0>
Subject: Re: [Doh] Seeking input on draft-03
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
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, 08 Feb 2018 19:57:04 -0000


On 08/02/18 18:05, Ben Schwartz wrote:
> 
> One important difference is that draft-03 no longer proposes a
> ".well-known" entry.  In draft-02 and prior, clients could check for the
> presence of a DOH service at the default path, given only the domain name
> of a server.  In draft-03, there is no default path, so clients must be
> configured with the full URL of the DOH endpoint.

Apologies if I'm forgetting a thread where this was discussed,
but what's the reason for dropping .well-known? (If there is a
thread, a pointer to that is a sufficient answer.)

Thanks,
S.

-- 
PGP key change time for me.
New-ID 7B172BEA; old-ID 805F8DA2 expires Jan 24 2018.
NewWithOld sigs in keyservers.
Sorry if that mucks something up;-)