Re: [Doh] DoH

Patrick McManus <mcmanus@ducksong.com> Thu, 28 March 2019 15:56 UTC

Return-Path: <mcmanus@ducksong.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 23735120013 for <doh@ietfa.amsl.com>; Thu, 28 Mar 2019 08:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=RKuXUHXY; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=lz/LavUE
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 n2Dk2moKMYjQ for <doh@ietfa.amsl.com>; Thu, 28 Mar 2019 08:56:08 -0700 (PDT)
Received: from outbound1f.eu.mailhop.org (outbound1f.eu.mailhop.org [52.28.59.28]) (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 6412B120003 for <doh@ietf.org>; Thu, 28 Mar 2019 08:56:07 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1553788565; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=W5EPh8UZwN1snnk7ULgp05MXvdnVn+MPyl0kbCN5P40o5OCP/0ufbN9IdUuigP8u5UIupbGHeSUAv bRqpKXmPqbVB1k08pveGJ+pCrz9P1+KvjZN2TtWdIMV4sGPUvmyOfHoNmDy9RVwwFSUHbpLr5u07bT mnaM6RxguzJm9ouP7xD/RTBLMKRacW+3wx17dEw5tlHLNn2M3lo4LfrUBBbbKHfxJZDA0dsy/vXqJV 6X/peFz3SdLb0m+1A7r7K1nSj7EzGmteLvbDvmtjBWM0FujcjlIR3mJMMkY2nR6kr3QhTg68HvAYle CVT/QVWcSAyZsUceynNpomfXwqTIVFA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=X4u204lVioXeth1noSIvFTeHalT6YWse+CC9NI+rpk8=; b=qZVl2OwqoWOm2/rVwDZmA4YXnL/ZbkHRGRx6PlpidWFpYYg25WF8AVjZh7VTqPHYGuWwoIy39xxJR qTq/NuuN4+yHITnXtKZU2mr23T3FBFYJFLEQHi9tbnk78yq+zG9EXTRGzVJo/B9kqrX7sFWqiMpCpp fdSETj7cAr8fMwUW22dsqGf6nCinudRsJrKWdCYZB3qiv/UtzPF4fTCh9RpQY82HvhB2Dk1U9rtXrJ 8wjNpf7cNfGbZ6H3NHWV7cODEEnD12WxajevTID7GbqsVh+nqRhdrgQQBOeyZ1oEHScwOVbyQvo/Lj zU0aKeBPQhGk4El8YxsiIVHiAM8IGIw==
ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.210.48; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=X4u204lVioXeth1noSIvFTeHalT6YWse+CC9NI+rpk8=; b=RKuXUHXYfin2pocG5E+mi+Vbj6lBmpRIefq8l+A4XVhKv7OWGLWF5zyQ65ZOa3KVAwpe/z0xNtwHL va167O2sFh4JBiCs6LdDiYy0BfsIXh4dJc5lvpjL0zdp92bP61nGmM6Vg7tMprdmc6iAs4WOKbt3io GMatZBaP9vGKeJ+Y=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=X4u204lVioXeth1noSIvFTeHalT6YWse+CC9NI+rpk8=; b=lz/LavUE9I21O5Cw38ZWlRANRKdhvxDMfSv+c9d36IDrmIUxsmMAFnTuiamF2bi2/Ivf8MoCCZIaj pRojlCZ4uODmU4cv7c5nWN+YzmKZOynszhm9nJ6kq+trgb/CHgVv90UHahoTS1kullSdROxRyNVTWh 557UQC3bgpN4ajInl90bztoBmuNXsOsS373m4lIK/a1ma1EIvojswdqMKAIT/K+LXEDYfLGIP2lFIg Lox1Nm2mI1uCPpmsKDSfKkJ2m7szRYOmDWxotO2drG05Z5jFinAuDXnLJgdFDWyYm13DabavhGOiBb s2vQvj6X0cz2ShQh2bsbmy8ik7YmwgQ==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: fc90aa87-5171-11e9-803b-31925da7267c
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.210.48
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-ot1-f48.google.com (unknown [209.85.210.48]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id fc90aa87-5171-11e9-803b-31925da7267c; Thu, 28 Mar 2019 15:56:03 +0000 (UTC)
Received: by mail-ot1-f48.google.com with SMTP id e5so18758713otk.12 for <doh@ietf.org>; Thu, 28 Mar 2019 08:56:02 -0700 (PDT)
X-Gm-Message-State: APjAAAVhkaaEA2ycDMFmyry56A5ZsjbdwyHi8xIBkU99rQfA6xJdpWMg eCb6ejzsFWsOT6XSneuqO+AatkWVjO90+gzURMw=
X-Google-Smtp-Source: APXvYqzZPH4yK3ghRV4pQDwEWTX5E35Lle9pxzAUnfor288TzK7D/pfhGF366RmAr7HIv2eBMBGNe9wpVYMP5qz5vRE=
X-Received: by 2002:a05:6830:183:: with SMTP id q3mr32577633ota.204.1553788561963; Thu, 28 Mar 2019 08:56:01 -0700 (PDT)
MIME-Version: 1.0
References: <DB7PR03MB4698C510EC609C85725FC158C6590@DB7PR03MB4698.eurprd03.prod.outlook.com>
In-Reply-To: <DB7PR03MB4698C510EC609C85725FC158C6590@DB7PR03MB4698.eurprd03.prod.outlook.com>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Thu, 28 Mar 2019 16:55:50 +0100
X-Gmail-Original-Message-ID: <CAOdDvNpJqaemDTHcUtTQ7Xc1cq5OOFU91qq_h97j6Uv1RTHD7A@mail.gmail.com>
Message-ID: <CAOdDvNpJqaemDTHcUtTQ7Xc1cq5OOFU91qq_h97j6Uv1RTHD7A@mail.gmail.com>
To: John Carr <john@johncarr.eu>
Cc: "paul.hoffman@icann.org" <paul.hoffman@icann.org>, "mcmanus@ducksong.com" <mcmanus@ducksong.com>, "doh@ietf.org" <doh@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004ac1d605852997ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/OmRd3ANGv8G-LGckNRyQsbaCtM4>
Subject: Re: [Doh] 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: Thu, 28 Mar 2019 15:56:11 -0000

Hi John - I cannot speak for the IETF, nor am I in a position to
effectively summarize all of the inputs over the year long process in
building RFC 8484. However the consensus opinion of that work is reflected
in that document. I can also refer you to the datatracker page for the
working group which includes the mailing list archives and minutes from in
person meetings while doing the work.
https://datatracker.ietf.org/group/doh/about/ The final consensus document
does contain some related content in section 10.

Best Regards,
-Patrick

On Thu, Mar 28, 2019 at 3:54 PM John Carr <john@johncarr.eu> wrote:

> Hi Both,
>
>
>
> I refer to the IETF project on DNS queries over HTTPS (DoH)
>
>
>
> Could you tell me if, in the course of the deliberations which have been
> taking place within the IETF structures in respect of DoH, any
> consideration was given, or is being given, to the implications of this
> standard in terms of its likely impact on filtering solutions which have
> been implemented either  on routers within individual households, or by
> ISPs or other access providers, where the purpose of the filtering is
> either to restrict access to known illegal content or it is to restrict
> access to content which is considered inappropriate, e.g. for younger
> family members?
>
>
>
> Many thanks,
>
>
>
> John  Carr
>
> Secretary
>
> Children’s Charities’ Coalition on Internet Safety
>
>
>
> www.chis.org.uk
>
>
>