Re: [Doh] Support requirements for Get and Post

"Hewitt, Rory" <rhewitt@akamai.com> Mon, 19 March 2018 22:05 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 5AA4112D955 for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 15:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 VH42jeCeDSac for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 15:05:44 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 B2C2F12D94D for <doh@ietf.org>; Mon, 19 Mar 2018 15:05:44 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2JM30HZ014991; Mon, 19 Mar 2018 22:05:44 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 : mime-version; s=jan2016.eng; bh=LOsE5JUTUr/fAPycJZoqVQbPeJQDwfh+mxnowp6mA9E=; b=FwqrVu7GpOQuKUfnrSZ655cfa9CKMnfu+GzB2LYtfZWqjhzW9+1a049fZ3/blC24Vxld xPOgg0xvZZ0v9AgNsw0G5VB/+8bv2jCz2tJqui1/qs4ugMJnCBoGFBiAz9DFp10izPaK Lyiq95rOP7xixbeT+Ku6COo6tppWrWT5TPern2Py/gmg6aMlQNxfdmRlk0ru8kaC39N0 MFVR1IWTn8MhLDviCa7kLrVA5PqgYqNBH3sqLESGYOv9tlLwcwHp+toZ2KI7OBgq/Ltk TtcXtH5ZkzfcFw/O8v40Hne/J/jB7q1Gt+pG5aovWMs9N14XB6Nr+UXfG+gRw7c1oJlC MA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0a-00190b01.pphosted.com with ESMTP id 2gruxkxp8t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 19 Mar 2018 22:05:44 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w2JLuhH8008829; Mon, 19 Mar 2018 18:05:39 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint1.akamai.com with ESMTP id 2grxbug6ad-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 19 Mar 2018 18:05:39 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 19 Mar 2018 18:05:38 -0400
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.1263.000; Mon, 19 Mar 2018 18:05:37 -0400
From: "Hewitt, Rory" <rhewitt@akamai.com>
To: =?utf-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, "doh@ietf.org" <doh@ietf.org>
Thread-Topic: [Doh] Support requirements for Get and Post
Thread-Index: AQHTvetL01SQQ5CXs0uHffNLDPsIYKPUoYOAgAAKFQCAAAdugIAAAR6AgAA8HwCAABL0AIABBnkAgAIU5wCAAAE4gIAAQoaA//++DdA=
Date: Mon, 19 Mar 2018 22:05:37 +0000
Message-ID: <043564f6d79c4077b93464fdeb8fabbb@usma1ex-dag1mb3.msg.corp.akamai.com>
References: <CAN6NTqzkUeF79y=heQ7PK7T3mQVDDk5WRtqB-npi6PuQ2s5bNQ@mail.gmail.com> <alpine.DEB.2.20.1803171337530.1331@tvnag.unkk.fr> <CAN6NTqykeU1gT0TaDKahBPeF-a8gwYG7gsAEK_aSE0fNP-AsfQ@mail.gmail.com> <CAOdDvNq7e5YGtUap6tHu34zX5q1PvmQjAh+fc0m=xcRDUrmKhA@mail.gmail.com> <CAOdDvNqGvPRH3SzP_tkHVZHr-geacqDBa+QfoqXGVxFWW2qr2A@mail.gmail.com> <CAHbrMsAkU+KKwCFpyLD40aPZLEVtRj=aEZsaC+=Y2yYwKCiEyA@mail.gmail.com> <CAOdDvNpFqavszS_OzOdOOd+e0E+ufDcqkyQzCrnAtWPZnKEZFQ@mail.gmail.com> <CAHbrMsBYcO_1v-dPKP8vvubqfjLyRJhZPsmHHE_ReVRiczbuYA@mail.gmail.com> <23215.63984.364570.759118@gro.dd.org> <CAOdDvNqVE3mDJ31fKs0zLY8Lu-Pt2oeZ2UtbOorz3=TeiaBxRg@mail.gmail.com> <958176d9-00cd-e8ba-8c74-c6c736ab99e8@nic.cz>
In-Reply-To: <958176d9-00cd-e8ba-8c74-c6c736ab99e8@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.117.176]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0031_01D3BF93.BCA9AAD0"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-19_12:, , 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-1711220000 definitions=main-1803190234
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-19_12:, , 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-1711220000 definitions=main-1803190235
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/O-MbA7Ey455dL5dI2HUm94uTEpA>
Subject: Re: [Doh] Support requirements for Get and Post
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, 19 Mar 2018 22:05:46 -0000

This thought has occurred to me also...

At an ABSOLUTE MINIMUM, we'd need GET for typical DNS requests and POST for e.g. AXFR. But if we didn't worry about AXFR (yet), then maybe only GET.

Of course, complex queries can get pretty out of hand size-wise, especially if we're passing a Base64-encoded udpwireformat query string...

Rory

-----Original Message-----
From: Petr Špaček [mailto:petr.spacek@nic.cz] 
Sent: Monday, March 19, 2018 3:00 PM
To: doh@ietf.org
Subject: Re: [Doh] Support requirements for Get and Post

On 19.3.2018 19:01, Patrick McManus wrote:
> this is an open issue I was planning to address with f2f time of the 
> wg as part of the slot related to this document (of course in addition 
> to any mailing list comments).
> 
> On Mon, Mar 19, 2018 at 5:57 PM, Dave Lawrence <tale@dd.org 
> <mailto:tale@dd.org>> wrote:
> 
>     Ben Schwartz writes:
>     > So does that mean that a DOH server and client that both comply with all
>     > SHOULD-strength requirements still may not be able to exchange any DNS data?
>     > That seems like a weaker guarantee of compatibility than is typical at the
>     > IETF.
> 
>     Has an answer to this question come through yet?
> 
>     > If following all the SHOULD-level recommendations is not sufficient
>     > to ensure compatibility, then as an implementor I would appreciate
>     > some clear additional guidance on what I have to do to make my
>     > client compatible with any compliant DOH server (and vice versa as a
>     > server implementor).
> 
>     Very much agree.
A subversive question:
Do we *actually* need GET and POST? Could we get away with just one of these?

Please apologize my lack of HTTP knowledge, but it seems to me weird to start with both (as opposed to gradual addition of new ones as necessary).

--
Petr Špaček  @  CZ.NIC

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