Re: [Doh] [Ext] Re: Use cases and URLs

Paul Hoffman <paul.hoffman@icann.org> Wed, 07 March 2018 05:28 UTC

Return-Path: <paul.hoffman@icann.org>
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 1326F126D73 for <doh@ietfa.amsl.com>; Tue, 6 Mar 2018 21:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 BVS2-GgxYo4N for <doh@ietfa.amsl.com>; Tue, 6 Mar 2018 21:28:23 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 397F2124D6C for <doh@ietf.org>; Tue, 6 Mar 2018 21:28:23 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 6 Mar 2018 21:28:21 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Tue, 6 Mar 2018 21:28:20 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: Adam Roach <adam@nostrum.com>
CC: "doh@ietf.org" <doh@ietf.org>
Thread-Topic: [Ext] Re: [Doh] Use cases and URLs
Thread-Index: AQHTtcdJ40hpyDl8sESf8pnHtAiHH6PErTiA//+Rbrc=
Date: Wed, 7 Mar 2018 05:28:19 +0000
Message-ID: <497ECCA2-5453-40CC-8385-7FEBE1A3FB0D@icann.org>
References: <24DEFAAB-D2A3-45E5-8CEE-E2E4EA23B9C2@icann.org>, <5bca3f4f-e40a-4afc-c71a-25ede395a065@nostrum.com>
In-Reply-To: <5bca3f4f-e40a-4afc-c71a-25ede395a065@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/d3H_Om92kNQ8haIjRpKjfiQ6haA>
Subject: Re: [Doh] [Ext] Re: Use cases and URLs
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: Wed, 07 Mar 2018 05:28:25 -0000

On Mar 6, 2018, at 20:04, Adam Roach <adam@nostrum.com>; wrote:
> 
>> On 3/6/18 9:49 PM, Paul Hoffman wrote:
>> The current draft says that there is no standard, and every origin will have its own URL for the API. This makes it much harder for a user to add new configured DNS API servers
> 
> 
> Can you elaborate on this a bit? I fully expect that the typical user-self-provisioning case will involve copy/pasting server information, in which case the difference between a server and a URL is pretty minimal. Do you expect users to type server names in rather than copying them?

Yes, exactly. If someone tells you that your bank runs this secure DNS server, that’s verbal, not copy and paste.