Re: [dns-privacy] Still interested in recursive-to-authoritative

Bill Woodcock <woody@pch.net> Fri, 18 May 2018 17:25 UTC

Return-Path: <woody@pch.net>
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 CA94D12D86B for <dns-privacy@ietfa.amsl.com>; Fri, 18 May 2018 10:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 ofrDnQAX0YvH for <dns-privacy@ietfa.amsl.com>; Fri, 18 May 2018 10:25:41 -0700 (PDT)
Received: from mail.pch.net (keriomail.pch.net [206.220.231.84]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 162D2126BF3 for <dns-privacy@ietf.org>; Fri, 18 May 2018 10:25:41 -0700 (PDT)
X-Footer: cGNoLm5ldA==
Received: from [85.248.21.171] ([85.248.21.171]) (authenticated user woody@pch.net) by mail.pch.net (Kerio Connect 9.2.5 patch 3) with ESMTPSA; Fri, 18 May 2018 10:25:33 -0700
Mime-Version: 1.0 (1.0)
In-Reply-To: <2b23569f-b5a0-c282-8b43-be4bffcfc147@innovationslab.net>
Date: Fri, 18 May 2018 19:25:28 +0200
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Message-Id: <292CC565-D85E-4BA1-9D70-13D0315DE500@pch.net>
References: <3AB1B0F3-8903-46C0-90A0-D62EF81A6062@vpnc.org> <2b23569f-b5a0-c282-8b43-be4bffcfc147@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
From: Bill Woodcock <woody@pch.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/IXXwGeBYytcBa5JOAxi8eXF-NcE>
Subject: Re: [dns-privacy] Still interested in recursive-to-authoritative
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: Fri, 18 May 2018 17:25:43 -0000

Speaking again for PCH and Quad9, we have, and the current draft incorporates our views. 

    
                -Bill


> On May 18, 2018, at 15:21, Brian Haberman <brian@innovationslab.net> wrote:
> 
> Hi All,
> 
>> On 5/16/18 4:03 PM, Paul Hoffman wrote:
>> While we wait for the charter update, I'd still like to find out who is
>> interested in pursuing draft-bortzmeyer-dprive-resolver-to-auth.
>> Personally, I think it is a good start on an important topic, but I
>> don't hear others supporting it on the list...
> 
> First, thanks to Paul for starting this query. The list has been quite
> silent since the London meeting.
> 
> Second, thanks to all the folks who have chimed in voicing support for
> an existing document.
> 
> What I will ask now is that those who are interested in the current
> draft to start providing detailed reviews of the draft to see if we can
> find some consensus on the approach. It is critical that these reviews
> come from both an implementation and an operational/deployment point of
> view.
> 
> Regards,
> Brian
> 
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy