Re: [DNSOP] New Version Notification for draft-jabley-dnsop-refuse-any-00.txt

Shane Kerr <shane@time-travellers.org> Thu, 01 October 2015 12:31 UTC

Return-Path: <shane@time-travellers.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 5AE7C1A8A3D for <dnsop@ietfa.amsl.com>; Thu, 1 Oct 2015 05:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 SrzznMFk3Dsi for <dnsop@ietfa.amsl.com>; Thu, 1 Oct 2015 05:31:03 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0E331ABD3A for <dnsop@ietf.org>; Thu, 1 Oct 2015 05:31:03 -0700 (PDT)
Received: from [2001:610:719:1:a417:530d:a63a:ee69] (helo=casual) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1Zhd0m-00058J-G9; Thu, 01 Oct 2015 12:31:00 +0000
Date: Thu, 01 Oct 2015 12:30:57 +0000
From: Shane Kerr <shane@time-travellers.org>
To: Dick Franks <rwfranks@acm.org>
Message-ID: <20151001123057.078c0635@casual>
In-Reply-To: <CAKW6Ri7dDB8pqrYiaBA6dw5qN=WCGVu8NNF4AgCXVn82VgT9wA@mail.gmail.com>
References: <20150930190405.17300.40441.idtracker@ietfa.amsl.com> <20151001025833.GA51655@isc.org> <0F438B6C-4797-4250-ABCA-4C5AE1D5F232@hopcount.ca> <20151001050850.GA51763@isc.org> <2EB63978-61F4-4833-8433-FDEE77CD4D65@hopcount.ca> <20151001101241.08ff8702@casual> <CAKW6Ri7dDB8pqrYiaBA6dw5qN=WCGVu8NNF4AgCXVn82VgT9wA@mail.gmail.com>
X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/k5QSaZBI_oG00Fh8bY3fzWjSN9g>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] New Version Notification for draft-jabley-dnsop-refuse-any-00.txt
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 01 Oct 2015 12:31:05 -0000

On 2015-10-01 12:13+0100
Dick Franks <rwfranks@acm.org> wrote:

> Dick Franks
> ________________________
> 
> 
> On 1 October 2015 at 11:12, Shane Kerr <shane@time-travellers.org> wrote:
> 
> >
> > In the case where people just want to reduce the damage of ANY queries
> > in reflection attacks, I quite like the PowerDNS option of forcing ANY
> > queries to TCP via truncation. I'm not sure if this has been documented
> > in any RFC, but if not then perhaps it bears mentioning too?
> >
> 
> That rests on two assumptions:
> 
> 1)  that damage limitation from reflection attacks is the primary concern
> here, which appears no longer to be the case.

The draft documents amplification attacks:

   ANY queries are also frequently used to exploit the amplification
   potential of DNS servers using spoofed source addresses and UDP
   transport (see [RFC5358]).  Having the ability to return small
   responses to such queries makes DNS servers less attractive
   amplifiers.

Which is why I mention it.

> 2) that there is some plausible reason for doing ANY queries, in which case
> it would be interesting to know what that might be.

The entire draft presumes some plausible reason for doing ANY queries,
otherwise it would just say "we hereby deprecate ANY queries". :P

In fact the start of the motivations section tries to address this:

   ANY queries are legitimately used for debugging and checking the
   state of a DNS server for a particular owner name.

I'm not sure I totally agree, since I have never had occasion to use an
ANY query in anger, but some people seem really attached to it.

Cheers,

--
Shane