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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 20 March 2014 15:38 UTC

Return-Path: <bortzmeyer@nic.fr>
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 2FD571A06D2 for <dns-privacy@ietfa.amsl.com>; Thu, 20 Mar 2014 08:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.414
X-Spam-Level:
X-Spam-Status: No, score=-0.414 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486] 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 ilujaTg6lbBY for <dns-privacy@ietfa.amsl.com>; Thu, 20 Mar 2014 08:38:15 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) by ietfa.amsl.com (Postfix) with ESMTP id BF86C1A03FD for <dns-privacy@ietf.org>; Thu, 20 Mar 2014 08:38:15 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 82BE43A780; Thu, 20 Mar 2014 16:38:06 +0100 (CET)
Received: by mail.sources.org (Postfix, from userid 1000) id 4FD3B190639; Thu, 20 Mar 2014 16:37:06 +0100 (CET)
Date: Thu, 20 Mar 2014 16:37:06 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Phillip Hallam-Baker <hallam@gmail.com>
Message-ID: <20140320153706.GA20076@sources.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dns-privacy/Eqrhp3XStq3GH8ubY78pUroPd4I
Cc: dns-privacy@ietf.org
Subject: Re: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dns-qname-minimisation-00.txt]
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: Thu, 20 Mar 2014 15:38:17 -0000

On Thu, Mar 20, 2014 at 11:09:34AM -0400,
 Phillip Hallam-Baker <hallam@gmail.com> wrote
 a message of 50 lines which said:

> minimization might well cause registries to take countermeasures if
> minimization was to affect their business models.

It's a general problem of security: the Bad Guys take
countermeasures. It was discussed in depth at the privacy tutorial at
the last IETF meeting, in London. Someone mentioned "business issues"
with privacy. And another one replied "anti-spam measures disturbed
some people's business, too".

> At the moment their servers support NS queries.  But if minimization
> is introduced they might change policy and start blocking.

This would be a violation of the protocol. We cannot prevent it but we
can at least call a spade a spade.

> the code might want to consider counter strategies. For example, if
> the request is for A records from secret.example.evil, it might
> query for A records as follows
>
> ? A, _.evil
> ? A, _.example.evil
> ? A, www.example.evil

Yes, good idea. "A" is probably the less revealing qtype. Should I add
this trick in the draft?