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

Warren Kumari <warren@kumari.net> Tue, 19 July 2016 12:02 UTC

Return-Path: <warren@kumari.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 A8F2712D5C2 for <dns-privacy@ietfa.amsl.com>; Tue, 19 Jul 2016 05:02:55 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 mcfgPiMNFaq8 for <dns-privacy@ietfa.amsl.com>; Tue, 19 Jul 2016 05:02:49 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A1E112D57B for <dns-privacy@ietf.org>; Tue, 19 Jul 2016 05:02:49 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id p74so13221910qka.0 for <dns-privacy@ietf.org>; Tue, 19 Jul 2016 05:02:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rr+wPjadvzRvxBZPQ974ECj0Ks7GFmqtCxZ5M1ZOLQQ=; b=N+WBQYJwPWjqjBZ3pVlG/UVhC1dcbYAIC2HGprEO/vwBQBLOwvw9OtODbSZYxtFe/v 9wKal9jWxuGoG9Js+h6vUnboexAHmpqYhNzoOVRAPBSmg+wEqc5tYhcXGDh0Xbgjglli ymngWskYCH1vt3b02zztiB+QvDDIjE+MjlFYjR3dWHW0/ZtxYCt19CLIoKejF148TrHd SXzXfS36eBqpovDPqCGsGy2HC0K3nIvldZW8hT65ki1HAFVecNyu0gI+cSzaWPe+K4TX QTA1vSDmQ6KYW6E+FEouLN+hvQPKpv5P+VQdV+F29fy/eDzvYqQa0JHZj1EFIdEt3zfv 0zZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rr+wPjadvzRvxBZPQ974ECj0Ks7GFmqtCxZ5M1ZOLQQ=; b=PAgh57WfkR9leLpeJTAVs99jxJAhmq0OiYCTLCHTg5JJNiCBpi2YNM7pKFAnf6G5ne lsQEHGqrpLxAVDN7oNdzjQC9U+3VhFGO4nfG7drz+QpikPYWmNYTQZGaZ6ScN+snHjfz W5cKBjFoFNrn6OWz5El/UcDS7PhEeMAwriBQOBmC/jRWTRFOZ5XbSuLVLbSsaohiGXmb 8On7o/JxIQ+midjusftVptT8PuQvgjISkZfEApTy7TDS9DQQKzqWTpZMjAoQnYWqgNAc oeDXMhqR5ML1w1zYBBV2YN5ZwDV2zt2WXCcT49qx12s1FtXlbSXjOLIm8kjq0CWUKIaX sTOw==
X-Gm-Message-State: ALyK8tIVQ3Wke1on4r4bWCmV7nHBzuZcW/n0nVo/QEu4p9ZZbTRI8YMTG8I9P2JIxaIQSd5qkAbOHDN1arGP2TRa
X-Received: by 10.55.6.148 with SMTP id 142mr50195817qkg.206.1468929768123; Tue, 19 Jul 2016 05:02:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.176.199 with HTTP; Tue, 19 Jul 2016 05:02:18 -0700 (PDT)
In-Reply-To: <D3B41EF4.963FE%terry.manderson@icann.org>
References: <20160718202546.GA6329@sources.org> <D3B41158.963D4%terry.manderson@icann.org> <20160719100213.3b46f96f@pallas.home.time-travellers.org> <D3B41EF4.963FE%terry.manderson@icann.org>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 19 Jul 2016 14:02:18 +0200
Message-ID: <CAHw9_iKTPYR_3uYahTdvPjxjNbH+rOVXaNhjiE=-+Z-TQJN5WA@mail.gmail.com>
To: Terry Manderson <terry.manderson@icann.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/2qo5mJHpXm9y8mzd3oMNJGEHZbM>
Cc: Shane Kerr <shane@time-travellers.org>, "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 12:02:55 -0000

On Tue, Jul 19, 2016 at 10:36 AM, Terry Manderson
<terry.manderson@icann.org> wrote:
> 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.


Yup, the chairs are perfectly happy for discussions about recursive to
auth to happen on this list, for people to write drafts and discuss
them, for meeting time to discuss these, etc -- however, we will give
priority to stuff which is in our current charter.

We will recharter to do the recursive to auth bit, but feel (along
with our AD) that we are not quite ready for that yet...

So, yes please, discussions and drafts -- and, even more importantly,
evidence of deployment of the current stuff...

W
>
> 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.
>>> >
>
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf