Re: [dns-privacy] Fwd: New Version Notification for draft-dickinson-bcp-op-00.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 13 March 2018 15:38 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C986B12D7F1 for <dns-privacy@ietfa.amsl.com>; Tue, 13 Mar 2018 08:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 ZcCIEVxPf7MK for <dns-privacy@ietfa.amsl.com>; Tue, 13 Mar 2018 08:38:48 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 8DDF9127419 for <dns-privacy@ietf.org>; Tue, 13 Mar 2018 08:38:48 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id CE80B2803B4; Tue, 13 Mar 2018 16:38:46 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id C88F32804F0; Tue, 13 Mar 2018 16:38:46 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id C1B112803B4; Tue, 13 Mar 2018 16:38:46 +0100 (CET)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id BC883642C581; Tue, 13 Mar 2018 16:38:46 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id B79684020F; Tue, 13 Mar 2018 16:38:46 +0100 (CET)
Date: Tue, 13 Mar 2018 16:38:46 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Sara Dickinson <sara@sinodun.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dns-privacy@ietf.org
Message-ID: <20180313153846.i6iaveokxce2ix7l@nic.fr>
References: <152027982666.31662.1887944342287645844.idtracker@ietfa.amsl.com> <CDE33D84-D4A6-46CC-8728-7B00CA84B401@sinodun.com> <20180312103115.ydcolb7hn2fjwoh6@nic.fr> <9B14F06C-1CC5-46CA-9E7B-60B48FC218A6@sinodun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <9B14F06C-1CC5-46CA-9E7B-60B48FC218A6@sinodun.com>
X-Operating-System: Debian GNU/Linux 9.3
X-Kernel: Linux 4.9.0-6-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.026411, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2018.3.13.152716
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/bJ5GLR1P1bu1YIbo5wDJITN_YDM>
Subject: Re: [dns-privacy] Fwd: New Version Notification for draft-dickinson-bcp-op-00.txt
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 15:38:51 -0000

On Mon, Mar 12, 2018 at 01:46:34PM +0000,
 Sara Dickinson <sara@sinodun.com> wrote 
 a message of 192 lines which said:

> Not sure, are you just suggesting we reference the terminology draft
> or we switch to using ‘public resolver’ (which strictly speaking
> isn’t defined there, just discussed)?

I suggest we use "public resolver", keeping "open resolver" for the
accidental ones. It seems well adopted.

> > > A .onion [RFC7686] service endpoint
> > 
> > I don't understand. You mean a public privacy-wise DNS resolver should
> > be a Tor entry node as well?
> 
> No, just a service offered via Tor. Maybe ‘endpoint’ is the
> confusion here and could be removed.

I still don't understand exactly what the DNS-privacy public resolver
must offer here.