Re: [DNSOP] Call for Adoption: draft-bortzmeyer-dns-qname-minimisation

Paul Vixie <paul@redbarn.org> Mon, 20 October 2014 21:21 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4941ACEE8 for <dnsop@ietfa.amsl.com>; Mon, 20 Oct 2014 14:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 GxXI3dtP3qFw for <dnsop@ietfa.amsl.com>; Mon, 20 Oct 2014 14:21:49 -0700 (PDT)
Received: from ss.vix.su (ss.vix.su [24.104.150.2]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5BA51ACEE7 for <dnsop@ietf.org>; Mon, 20 Oct 2014 14:21:49 -0700 (PDT)
Received: from [IPv6:2600:1003:b128:59a0:6c3f:6eb5:e8da:568e] (unknown [IPv6:2600:1003:b128:59a0:6c3f:6eb5:e8da:568e]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.su (Postfix) with ESMTPSA id 1C522EBC94 for <dnsop@ietf.org>; Mon, 20 Oct 2014 21:21:48 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <54457CE9.1090208@redbarn.org>
Date: Mon, 20 Oct 2014 14:21:45 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.11 (Windows/20140602)
MIME-Version: 1.0
To: dnsop <dnsop@ietf.org>
References: <54336646.1040804@gmail.com> <CAMm+LwjA=Pq8GzKvo9D8HdvLyNbZHOVF6m9hYFdOxaXuHXyt4A@mail.gmail.com> <CAMm+LwgrQBSXtazBR8MY9mso-Wc5B8KcCWOn8ymqvL=nbg+RJw@mail.gmail.com>
In-Reply-To: <CAMm+LwgrQBSXtazBR8MY9mso-Wc5B8KcCWOn8ymqvL=nbg+RJw@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/alternative; boundary="------------040406030504000408040102"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/z8uo7M1SOENINTorWfSv_Y1NTv0
Subject: Re: [DNSOP] Call for Adoption: draft-bortzmeyer-dns-qname-minimisation
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Oct 2014 21:21:51 -0000

this is a +1. see below.

> Phillip Hallam-Baker <mailto:phill@hallambaker.com>
> Monday, October 20, 2014 12:04 PM
> Just to expand on my comments after some arguments made against.
>
> The reason I think the WG should adopt the work item is that the
> original design of DNS is now defective in the light of contemporary
> privacy concerns. There is no reason that the operators of registries
> should have sight of any information they do not have a need to know.
>
> The business relationships built up over the years on the assumption
> that this data will be available and for sale to the highest bidder
> are of neither consequence nor concern.
>
> These practices are going to be insisted on regardless of choices made
> by this group. If indeed minimization has operational effects it is
> much better to document them and allow parties to avoid unintended
> consequences. At this point however, there is no evidence of harm. 
>
> Proof of very substantial showing of harm should be necessary to block
> consideration of a proposal at the outset. Opponents will after all
> have plenty of time to make objections in WG process, that being the
> point of WG process. 
>
> It would be a terrible mistake to reject this work without a hearing
> because of the mere possibility that a problem could occur. If indeed
> the state of the DNS is as fragile as is suggested it will soon
> collapse of its own accord. I rather suspect however that the fears
> are unfounded.

+1, to all observations above.

-- 
Paul Vixie