Re: [DNSOP] Benoit Claise's No Objection on draft-ietf-dnsop-root-loopback-04: (with COMMENT)

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 29 September 2015 22:54 UTC

Return-Path: <paul.hoffman@vpnc.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 5C6FC1A0180; Tue, 29 Sep 2015 15:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
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 TJWltfu5v_7J; Tue, 29 Sep 2015 15:54:08 -0700 (PDT)
Received: from hoffman.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 919131A0169; Tue, 29 Sep 2015 15:54:08 -0700 (PDT)
Received: from [10.32.60.79] (142-254-17-123.dsl.dynamic.fusionbroadband.com [142.254.17.123]) (authenticated bits=0) by hoffman.proper.com (8.15.1/8.14.9) with ESMTPSA id t8TMkhf1086777 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Sep 2015 15:46:44 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-123.dsl.dynamic.fusionbroadband.com [142.254.17.123] claimed to be [10.32.60.79]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Benoit Claise <bclaise@cisco.com>
Date: Tue, 29 Sep 2015 15:46:43 -0700
Message-ID: <FEBF6503-9A94-4BFD-A4E1-D0E683784CFE@vpnc.org>
In-Reply-To: <20150928135358.25443.47441.idtracker@ietfa.amsl.com>
References: <20150928135358.25443.47441.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/_73W4i_1JE1KKtUa4tKDwY7cYTc>
Cc: tjw.ietf@gmail.com, draft-ietf-dnsop-root-loopback@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-root-loopback.ad@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-dnsop-root-loopback.shepherd@ietf.org
Subject: Re: [DNSOP] Benoit Claise's No Objection on draft-ietf-dnsop-root-loopback-04: (with COMMENT)
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: Tue, 29 Sep 2015 22:54:09 -0000

On 28 Sep 2015, at 6:53, Benoit Claise wrote:

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>  Malicious third
>  parties might be able to observe that traffic on the network between
>  the recursive resolver and one or more of the DNS roots
>  ....
>  The primary goals of this design is to provide faster negative
>  responses to stub resolver queries that contain junk queries, and to
>  prevent queries and responses from being visible on the network.
>
> I've been wondering. So this mechanism is basically to speed up junk
> queries.
> What can a malicious third party do by observing junk queries. 
> Nothing, I
> guess.

Actually, seeing junk queries can leak some valuable information. For 
example, imagine that some malware sends junk queries for a known name; 
seeing that can be valuable information for someone watching the stream 
of requests. There are some companies whose business model include 
watching cache misses in recursive resolvers for interesting patterns.

> I guess you want something like.
> OLD:
>  The primary goals of this design is to provide faster negative
>  responses to stub resolver queries that contain junk queries, and to
>  prevent queries and responses from being visible on the network.
>
> NEW:
>  The primary goals of this design is to provide faster negative
>  responses to stub resolver queries that contain junk queries, and to
>  prevent valid queries and responses from being visible on the 
> network.

Given the above, we would like to leave the text as-is because some 
recursive operators care about exposure of bad queries as well.

--Paul Hoffman and Warren Kumari