IETF Logo Mail Archive

Re: [Doh] Changes in draft-ietf-doh-resolver-associated-doh-01

"Hewitt, Rory" <rhewitt@akamai.com> Thu, 07 March 2019 00:36 UTC

Return-Path: <rhewitt@akamai.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 33AAE13127C for <doh@ietfa.amsl.com>; Wed, 6 Mar 2019 16:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level:
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.468, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 4BJehsb3-MD7 for <doh@ietfa.amsl.com>; Wed, 6 Mar 2019 16:36:40 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 9ED9C131146 for <doh@ietf.org>; Wed, 6 Mar 2019 16:36:40 -0800 (PST)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x270WGHC018464 for <doh@ietf.org>; Thu, 7 Mar 2019 00:36:39 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=KVo7B/t1FvobRRbiSuvdpuQs78gDik5E5kjikKkNJis=; b=Ki987ZnB9ogOe2MDldxKRyPFjzN7+ifs75+uB7IMDN4+ZqEZInZ8+bX6a/SrrBqfNKCP l+d+8xyzeVi5OiD+HUyVVJJUvY+w9QkfsQm3pLpVdrJx8Lr3hHm+SEE5Yc5BaSiBhkW4 5LJpBO5e1W7af+1iyp+o1vXmZz/moU6Wm/kztKgYIlYuFJvj6AjrR11ovzOvylEoZTtc I2YwT3gHn4Dftlr7vu2V3n+IqbHHx8TC8tVr8XaSN41Rm9KFtBsmgi8dRgD0XOiWV9Su OcWA/QK/gxwly2cxIa7OeaEqpBNo3dZ1C4+0Bcy9XUlGLK+MqTmJyW7CHOJHLIjyfJPc tw==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0b-00190b01.pphosted.com with ESMTP id 2r2nrk8kc8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <doh@ietf.org>; Thu, 07 Mar 2019 00:36:39 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x270ZZnb012697 for <doh@ietf.org>; Wed, 6 Mar 2019 19:36:39 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint1.akamai.com with ESMTP id 2qyp20uypg-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <doh@ietf.org>; Wed, 06 Mar 2019 19:36:37 -0500
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb1.msg.corp.akamai.com (172.27.123.60) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Mar 2019 19:36:35 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Mar 2019 19:36:35 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.003; Wed, 6 Mar 2019 19:36:34 -0500
From: "Hewitt, Rory" <rhewitt@akamai.com>
To: DoH WG <doh@ietf.org>
Thread-Topic: Changes in draft-ietf-doh-resolver-associated-doh-01
Thread-Index: AQHU1HtaKW7Yd31zOk+Dlru9pnF9OKX/T7aw
Date: Thu, 07 Mar 2019 00:36:34 +0000
Message-ID: <69e135a6a4bf43dc956fa50c30624a8b@usma1ex-dag1mb3.msg.corp.akamai.com>
References: <784FED62-3169-4919-8756-FD48DEA9EA45@icann.org>
In-Reply-To: <784FED62-3169-4919-8756-FD48DEA9EA45@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.112.243]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-06_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903070001
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-06_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903070001
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/pm67Cmp5TSDFpDwx2JlZtkU50Ns>
Subject: Re: [Doh] Changes in draft-ietf-doh-resolver-associated-doh-01
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: Thu, 07 Mar 2019 00:36:42 -0000

Paul,

In Sec 2.1, could we see an example TXT record?

If multiple TXT records are returned, in addition to the URI template itself, can each contain some indication of priority (similar to MX records) and/or re-resolving strategies (round-robin, etc.) to apply across the set of TXT records?

In Sec  2.2, for [[ Need to talk about what a response with an empty list means ]], it would be simplest to return a 501 Not Implemented, no?

Rory

-----Original Message-----
From: Paul Hoffman <paul.hoffman@icann.org> 
Sent: Wednesday, March 6, 2019 4:19 PM
To: DoH WG <doh@ietf.org>
Subject: [Doh] Changes in draft-ietf-doh-resolver-associated-doh-01

If you looked at the diff, you'll know: it's pretty much a complete reorganization based on comments that I got that the order and style of the three protocols defined in the document made it hard to determine which protocol did what. The discussion about web applications was reduced to a minimum. Also, the details for "DoH Servers from HTTPS" were filled in; it is now definitely JSON returned.

Feel free to comment. There is still more to do here.

--Paul Hoffman

_______________________________________________
Doh mailing list
Doh@ietf.org
https://www.ietf.org/mailman/listinfo/doh

v2.23.0 | Report a Bug | By Email