Re: [Doh] WGLC on draft-ietf-doh-dns-over-https

Mateusz Jończyk <mat.jonczyk@o2.pl> Mon, 07 May 2018 09:11 UTC

Return-Path: <mat.jonczyk@o2.pl>
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 4AD6D126B6D for <doh@ietfa.amsl.com>; Mon, 7 May 2018 02:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 0wv_nkY04jDL for <doh@ietfa.amsl.com>; Mon, 7 May 2018 02:11:28 -0700 (PDT)
Received: from mx-out.tlen.pl (mx-out.tlen.pl [193.222.135.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCFE8124BE8 for <doh@ietf.org>; Mon, 7 May 2018 02:11:27 -0700 (PDT)
Received: (wp-smtpd smtp.tlen.pl 11333 invoked from network); 7 May 2018 11:11:24 +0200
Received: from acle104.neoplus.adsl.tpnet.pl (HELO [192.168.1.22]) (mat.jonczyk@o2.pl@[83.10.106.104]) (envelope-sender <mat.jonczyk@o2.pl>) by smtp.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP for <doh@ietf.org>; 7 May 2018 11:11:24 +0200
From: =?UTF-8?Q?Mateusz_Jo=c5=84czyk?= <mat.jonczyk@o2.pl>
To: DoH WG <doh@ietf.org>
References: <56fb94bd-ec0f-81c8-16c8-8391ef1a5f46@o2.pl>
Openpgp: preference=signencrypt
Message-ID: <02d1ab18-a10d-0aaa-ceed-32ef9e6403e6@o2.pl>
Date: Mon, 7 May 2018 11:11:12 +0200
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <56fb94bd-ec0f-81c8-16c8-8391ef1a5f46@o2.pl>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7jQ9vTJDPBA2UczRQWivKRncsclaqj59C"
X-WP-MailID: 4222b65be1e834cc8aa204b20e2f4c48
X-WP-AV: skaner antywirusowy Poczty o2
X-WP-SPAM: NO 000000A [sYNk]
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/z9Gd6hua0sfa_6gJF5dElEg_Oec>
Subject: Re: [Doh] WGLC on draft-ietf-doh-dns-over-https
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: Mon, 07 May 2018 09:11:31 -0000

W dniu 05.05.2018 o 18:17, Mateusz Jończyk pisze:
> what should the phrase "is a trusted service for the DOH query" mean?
> Is it possible that for some DOH queries the request URI is trusted and for some
> others isn't?
> 
> 
> I would propose simply the following text for the "# Security" section:
> 	When DNSSEC is not used, a DNS API server can give the client invalid
> 	data as a response to a DNS query. Therefore, a DNS API client SHOULD
> 	carefully determine which DNS API server(s) it trusts. For example, a
> 	DNS API client can have trusted DNS API server(s) preconfigured.
> 
> I suppose that most computer users won't know what a DNS is and won't configure
> a DNS API server themselves. Therefore "explicit configuration" in practice
> means "preconfigured DNS API server(s)".
> 

I have received no response, so I have sent a corresponding pull request:
	https://github.com/dohwg/draft-ietf-doh-dns-over-https/pull/175

Greetings,
Mateusz Jończyk