Re: [Doh] [Ext] Consensus confirmation

Paul Hoffman <paul.hoffman@icann.org> Mon, 26 March 2018 05:25 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 2C61C1252BA for <doh@ietfa.amsl.com>; Sun, 25 Mar 2018 22:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 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] 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 y_Xyg6CyF5Ii for <doh@ietfa.amsl.com>; Sun, 25 Mar 2018 22:25:28 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31E33120047 for <doh@ietf.org>; Sun, 25 Mar 2018 22:25:28 -0700 (PDT)
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 Microsoft SMTP Server (TLS) id 15.0.1178.4; Sun, 25 Mar 2018 22:25:26 -0700
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; Sun, 25 Mar 2018 22:25:26 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: DoH WG <doh@ietf.org>
Thread-Topic: [Ext] [Doh] Consensus confirmation
Thread-Index: AQHTxFbYsQ9E3J/CBUiMSvMzE1ngdKPiclkA
Date: Mon, 26 Mar 2018 05:25:25 +0000
Message-ID: <E40FD111-0316-426F-AC43-38F75FE46893@icann.org>
References: <CAHbrMsAs8G-eW7DTUtbdGukLszHohmk4NHhFPWw01+h3-v9Uog@mail.gmail.com>
In-Reply-To: <CAHbrMsAs8G-eW7DTUtbdGukLszHohmk4NHhFPWw01+h3-v9Uog@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_B3DBCEA6-D385-44DD-8ECE-F1926A3E10FB"; protocol="application/pgp-signature"; micalg="pgp-sha256"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/D8-_VM5qTpkEtlGWzEWnKrspI1Y>
Subject: Re: [Doh] [Ext] Consensus confirmation
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, 26 Mar 2018 05:25:29 -0000

> 1. Should we have a content-type that is Mandatory to Implement?
> 
> Several participants spoke in favor of making the default format (currently called "application/dns-udpwireformat") mandatory, at least for servers.

application/dns-udpwireformat needs to be mandatory to implement for us to have maximum interoperability out of the box.

> 2. Among the GET and POST modes of operation, which, if any, should be mandatory to implement?
> 
> Among the participants, there was consensus in favor of making both GET and POST mandatory to implement for servers.

Both GET and POST need to be mandatory to implement for servers so that we have maximum interoperability out of the box.

--Paul HOffman