[Doh] New draft, seeking comments in DNSOP: draft-sah-resolver-information

Paul Hoffman <paul.hoffman@icann.org> Tue, 30 April 2019 21:00 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D4D1612016C for <doh@ietfa.amsl.com>; Tue, 30 Apr 2019 14:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id M3LupLF26j2p for <doh@ietfa.amsl.com>; Tue, 30 Apr 2019 14:00:47 -0700 (PDT)
Received: from mail.icann.org (out.west.pexch112.icann.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88BBD12015C for <doh@ietf.org>; Tue, 30 Apr 2019 14:00:47 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org ( by PMBX112-W1-CA-1.pexch112.icann.org ( with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 30 Apr 2019 14:00:46 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1367.000; Tue, 30 Apr 2019 14:00:46 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: doh WG <doh@ietf.org>
Thread-Topic: New draft, seeking comments in DNSOP: draft-sah-resolver-information
Thread-Index: AQHU/5fH8aBwa2M3dkGJ3lqDMHKOVg==
Date: Tue, 30 Apr 2019 21:00:45 +0000
Message-ID: <7872F13E-61C5-491B-88EB-C60F0F3AC2D4@icann.org>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <342D7F9840E9384BB482D7EFEAC16631@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/-JDc7HFNwj3Vv4FLt0oGwLXsyKQ>
Subject: [Doh] New draft, seeking comments in DNSOP: draft-sah-resolver-information
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: Tue, 30 Apr 2019 21:00:49 -0000

Greetings again. Puneet, Roy and I have just published a -00 with an idea for how to get information about a recursive resolver from the resolver, if it wants to give that information. This is an outgrowth of my earlier work in the DOH WG on draft-ietf-doh-resolver-associated-doh. The discussion on that latter draft in Prague had a couple of people saying "this should be more general than just DoH" and "what about DoT", which sparked the idea for draft-sah-resolver-information.

We have started the discussion in DNSOP because the draft covers much more than DoH. If DNSOP folks think that the idea has legs, I would ask the DOH WG to drop discussion of draft-ietf-doh-resolver-associated-doh in favor of the new draft. If not, I'll keep working on draft-ietf-doh-resolver-associated-doh here.

--Paul Hoffman