Re: [dns-privacy] DPRIVE next steps

Tim Wicinski <tjw.ietf@gmail.com> Mon, 24 November 2014 22:06 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34F501ACCE2 for <dns-privacy@ietfa.amsl.com>; Mon, 24 Nov 2014 14:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 TUqEqaf931be for <dns-privacy@ietfa.amsl.com>; Mon, 24 Nov 2014 14:05:58 -0800 (PST)
Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E28A1ACCE1 for <dns-privacy@ietf.org>; Mon, 24 Nov 2014 14:05:58 -0800 (PST)
Received: by mail-qc0-f180.google.com with SMTP id i8so7689162qcq.11 for <dns-privacy@ietf.org>; Mon, 24 Nov 2014 14:05:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=s4otQ+2yOqCTgj2nfU+kvvJPyAPm+M2iS4RD3XL4fJk=; b=SeQAFZkLIMl1Mml8SLE3DUBx053FpjW1ebrBgOHWQi+iatXYDystYTK252Ilu4Pi6J hbuExI33X1onrPuxvdAN1DUo3Rqp7lgnQkNcoxOtCklAB+bEdm1d+AI9WwO4uAAVELS0 gQGXZoSv9OBcPwy+k1YLhShgy+BkOiBwktRvV2QuL4/5vPTYF0+TbQZeX92Dxvt7zw8M ATqNcofvVcO/YptU6lwun2OQ0jcTcCazH//4HkOEhdulPOrSIze4C5aMxoejlsLyaxJp bnZ4H1pegogNcF1kYKNRNHWUTIW6kOVi0vQhYXeuarzpw4WRohEMqpa8GuHysEdE4lq8 b1ew==
X-Received: by 10.140.95.225 with SMTP id i88mr31379416qge.2.1416866757303; Mon, 24 Nov 2014 14:05:57 -0800 (PST)
Received: from still.local (50-121-209-253.drr03.clbg.wv.frontiernet.net. [50.121.209.253]) by mx.google.com with ESMTPSA id a9sm13019943qgf.7.2014.11.24.14.05.56 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Nov 2014 14:05:56 -0800 (PST)
Message-ID: <5473ABC3.1080804@gmail.com>
Date: Mon, 24 Nov 2014 17:05:55 -0500
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Thunderbird/34.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <ietf@hallambaker.com>
References: <5473A1A8.4010100@gmail.com> <CAMm+Lwgo4aa2BVuPpYB1aQ7ztg5CWcEMB-XFjcD7YAoTmMHOog@mail.gmail.com>
In-Reply-To: <CAMm+Lwgo4aa2BVuPpYB1aQ7ztg5CWcEMB-XFjcD7YAoTmMHOog@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dns-privacy/wAeipy7g1BjB_s53piUxkz1OL4A
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Subject: Re: [dns-privacy] DPRIVE next steps
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 24 Nov 2014 22:06:00 -0000

Philip,

I did not say a requirements document. I said the Problem Statement, and 
evaluation metrics.  Neither are requirements.

I do not expect to spend six weeks bike shedding use cases.  I believe 
we can move both of these forward before Dallas, if sufficient energy is 
put into them.

tim


On 11/24/14 5:02 PM, Phillip Hallam-Baker wrote:
> On Mon, Nov 24, 2014 at 4:22 PM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>
>> (I was waiting to confirm the wording with Warren, but I failed to remember
>> he was away last week).
>>
>> Coming out of IETF91, we saw good discussion around the problem statement;
>> the beginnings of a discussion around evaluation metrics; and several
>> different solutions searching for the appropriate problem.
>
> And how do we go about that?
>
> The reason I am very skeptical of the value of requirements exercises
> in IETF is that my experience is that they are almost invariably a
> proxy fight for the solution space and in particular a fight to frame
> the requirements so that a particular favored solution is the winner.
>
> Which is why I believe that requirements capture should be driven by
> use cases and there should be NO discussion of whether the use cases
> are valid or not. Bear me out on this, I see no point in spending six
> weeks arguing about whether a use case is important or not or what the
> relative order of priority should be. Such efforts are invariably an
> underhand approach to constraining the solution space so that the
> favored proposal wins.
>
>
> Rather than developing a requirements document, a Wiki would be much
> more appropriate. And no need to turn it into an RFC either.
>
> I am sure that if you narrow the scope of the work down it is possible
> to find a viewpoint from which the differences between them disappear.
> But what is the point in doing that? The point is to make a decision
> and to make a decision, differences are useful.
>
>
>> Then we would like to see some action on the evaluation document. I know
>> when I spoke with Allison they were having some resource scheduling
>> conflicts, and I had offered to assist with the document if there was a
>> working outline. Perhaps others will feel so inclined.
>
> I submitted such a framework some time ago:
>
> http://tools.ietf.org/html/draft-hallambaker-dnse-02
>