IETF Logo Mail Archive

Re: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dprive-step-2-00.txt]

Terry Manderson <terry.manderson@icann.org> Tue, 19 July 2016 08:36 UTC

Return-Path: <terry.manderson@icann.org>
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 8277012DC4E for <dns-privacy@ietfa.amsl.com>; Tue, 19 Jul 2016 01:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.488
X-Spam-Level:
X-Spam-Status: No, score=-5.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, 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 rANrqjt8uF9M for <dns-privacy@ietfa.amsl.com>; Tue, 19 Jul 2016 01:36:11 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0545B12D16C for <dns-privacy@ietf.org>; Tue, 19 Jul 2016 01:36:11 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 19 Jul 2016 01:36:08 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Tue, 19 Jul 2016 01:36:08 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Shane Kerr <shane@time-travellers.org>
Thread-Topic: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dprive-step-2-00.txt]
Thread-Index: AQHR4TL2yWwRf1JMHU+weYicu48PsKAgeIGA//9iKICAALEagA==
Date: Tue, 19 Jul 2016 08:36:08 +0000
Message-ID: <D3B41EF4.963FE%terry.manderson@icann.org>
References: <20160718202546.GA6329@sources.org> <D3B41158.963D4%terry.manderson@icann.org> <20160719100213.3b46f96f@pallas.home.time-travellers.org>
In-Reply-To: <20160719100213.3b46f96f@pallas.home.time-travellers.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3551798165_7165337"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/eThMctPGL4cdgv4sSZBtLhHYXFQ>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dprive-step-2-00.txt]
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Jul 2016 08:36:13 -0000

Hi Shane,

I also agree that recursive-to-authority privacy should be done in dprive,
and a my desire here is two fold. So yes the developed, but essentially
not yet deployed, standards need to bake. Additionally I feel that
deployment experience as very important input to the next step.

I'm also not insisting folks work outside of the working group. I'll leave
it to the chairs to take (or not) informative presentations at future
meetings on related dprive topics, yet surely priority should be given to
the charter as it stands.

IIRC the consensus at the time for forming dprive as a WG was to first see
a baked stub-recursive solution with experience. I still feel that has
value and feel it's premature to dive into recursive-to-authority in
charter space despite the very good intentions of smart people in this
working group.

Cheers
Terry

On 19/07/2016, 6:02 PM, "Shane Kerr" <shane@time-travellers.org> wrote:

>Terry,
>
>I think it's weird that we have people who have ideas about needed
>standardization work, and we insist that they work outside of a
>chartered working group.
>
>I tend to think that recursive-to-authority privacy work should be done
>in dprive, but if that working group needs to wait for the standards
>they have developed to "bake", then okay. We should work towards a BoF
>for a new working group then, right?
>
>Cheers,
>
>--
>Shane
>
>At 2016-07-19 07:27:13 +0000
>Terry Manderson <terry.manderson@icann.org> wrote:
> 
>> Thanks for starting to enumerate the options/problems related to
>>recursive
>> resolver to authoritative name server.
>> 
>> As AD, I would very much like to see some operational data points and
>>some
>> experience from 'the wild' of deployment to better inform a (re)charter
>> discussion.
>> 
>> That said, I am VERY interested to see individuals start work (as you
>>have
>> done) and continue to work in parallel with the above goals.
>> 
>> Cheers
>> Terry
>> 
>> On 19/07/2016, 6:25 AM, "dns-privacy on behalf of Stephane Bortzmeyer"
>> <dns-privacy-bounces@ietf.org on behalf of bortzmeyer@nic.fr> wrote:
>> 
>> >Isn't it time we start working on the resolver-to-auth link?
>> >
>> >I know that DPRIVE does not meet in Berlin but, if people who are
>> >there (I'm not) want to discuss it, I'll be interested in feedbacks,
>> >flames and pull requests.
>> >

v2.23.0 | Report a Bug | By Email