Re: [DNSOP] my lone hum against draft-wkumari-dnsop-multiple-responses

"Ralf Weber" <dns@fl1ger.de> Wed, 20 July 2016 12:48 UTC

Return-Path: <dns@fl1ger.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1064012D0F0 for <dnsop@ietfa.amsl.com>; Wed, 20 Jul 2016 05:48:10 -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_PASS=-0.001] autolearn=ham autolearn_force=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 dm4Ax-qZmUyR for <dnsop@ietfa.amsl.com>; Wed, 20 Jul 2016 05:48:08 -0700 (PDT)
Received: from smtp.guxx.net (smtp.guxx.net [IPv6:2a01:4f8:a0:322c::25:42]) by ietfa.amsl.com (Postfix) with ESMTP id 08BD312D53C for <dnsop@ietf.org>; Wed, 20 Jul 2016 05:48:08 -0700 (PDT)
Received: by nyx.guxx.net (Postfix, from userid 107) id 5DE025F40410; Wed, 20 Jul 2016 14:48:07 +0200 (CEST)
Received: from [64.89.232.131] (dhcp-b26b.meeting.ietf.org [31.133.178.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id D0F4B5F4015F; Wed, 20 Jul 2016 14:48:06 +0200 (CEST)
From: Ralf Weber <dns@fl1ger.de>
To: 延志伟 <yzw_iplab@163.com>
Date: Wed, 20 Jul 2016 14:48:07 +0200
Message-ID: <7B0A7E9E-44DE-4F1D-87F3-6D545942BCC4@fl1ger.de>
In-Reply-To: <42f33e57.db83.156084ec312.Coremail.yzw_iplab@163.com>
References: <b00ec4.3833.15606420d47.Coremail.yzw_iplab@163.com> <236F5488-42D4-4A89-ACAB-B55FD2B5782A@fl1ger.de> <3f3d0268.51bf.15606cbef7f.Coremail.yzw_iplab@163.com> <CB723A3C-8DE8-4E01-AC08-94161CCB5468@fl1ger.de> <42f33e57.db83.156084ec312.Coremail.yzw_iplab@163.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RLfm5jTUzqeq1wOp6TXn6JsmwOU>
Cc: ietf@hardakers.net, dnsop@ietf.org
Subject: Re: [DNSOP] my lone hum against draft-wkumari-dnsop-multiple-responses
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 20 Jul 2016 12:48:10 -0000

Moin!

On 20 Jul 2016, at 14:36, 延志伟 wrote:
> But anyway, let's go back to the scenario considered by our draft to 
> illustrate its necessity.
> I show an example as following (although I think we have described it 
> several times. :-)):
> In order to visit the www.baidu.com, the user has to query 
> www.baidu.com and many other related domain names
> (for many related resources such as images, java script, html, flash, 
> video, sound), then a series of queries happen as the attached figure 
> shows.
So what. If your recursive resolver is used by many people these records 
will be in the cache. There will be no gain. Now of course if your 
resolver only serves you that might be the case, but that is not the way 
DNS was designed or is operated today. Oh and your example have out of 
zone queries (also very common like facebook.com asking for fbcdn.com) 
that can not be solved by this anyway. There is no better tool than a 
prefetching hot resolver for lots of users to solve this problem.

So long
-Ralf