Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh

<nigel.tedeschi@bt.com> Fri, 08 February 2019 17:57 UTC

Return-Path: <nigel.tedeschi@bt.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 0B09D1294FA for <doh@ietfa.amsl.com>; Fri, 8 Feb 2019 09:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 BPKsIc6V-Up6 for <doh@ietfa.amsl.com>; Fri, 8 Feb 2019 09:57:47 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [62.239.224.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D257A124BF6 for <doh@ietf.org>; Fri, 8 Feb 2019 09:57:46 -0800 (PST)
Received: from tpw09926dag07h.domain1.systemhost.net (10.9.202.46) by RDW083A012ED68.bt.com (10.187.98.38) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 8 Feb 2019 17:55:23 +0000
Received: from tpw09926dag07f.domain1.systemhost.net (10.9.202.38) by tpw09926dag07h.domain1.systemhost.net (10.9.202.46) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 8 Feb 2019 17:57:42 +0000
Received: from tpw09926dag07f.domain1.systemhost.net ([fe80::39eb:b031:eb4f:b2c9]) by tpw09926dag07f.domain1.systemhost.net ([fe80::39eb:b031:eb4f:b2c9%12]) with mapi id 15.00.1395.000; Fri, 8 Feb 2019 17:57:42 +0000
From: <nigel.tedeschi@bt.com>
To: <doh@ietf.org>
Thread-Topic: Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh
Thread-Index: AdS/168z1HbSsezNSMeCO3LqHus/Gw==
Date: Fri, 8 Feb 2019 17:57:42 +0000
Message-ID: <fb31ef17a8a34557a3582fecf1b659c0@tpw09926dag07f.domain1.systemhost.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.9.202.242]
Content-Type: multipart/alternative; boundary="_000_fb31ef17a8a34557a3582fecf1b659c0tpw09926dag07fdomain1sy_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/CiToDi1KO1E4Zmssxs93Oey53Pk>
Subject: Re: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh
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: Fri, 08 Feb 2019 18:00:19 -0000

WRT the draft - from an ISP perspective we agree it makes sense that it be adopted somewhere, probably not the DoH WG? We share concerns mentioned before that it'd be better to take a more holistic view of DNS services discovery. As an example within a discovery algorithm, are we indicating DoH represents the Apex of possible DNS solution choices? This Apex question becomes more interesting when an application doesn't include a UI to capture a user's choice from a shortlist.



Additionally, many ISPs provide "parental controls / content blocking capabilities",  & Malware detection capabilities at a customer's request, it might be useful to understand how these higher layer services, might be maintained within an overarching DNS discovery service?



Regards

Nigel Tedeschi