Re: [Inip-discuss] Innovation in DNS

Bauyrzhan Askar <mail@ainasystem.org> Thu, 25 August 2016 16:14 UTC

Return-Path: <mail@ainasystem.org>
X-Original-To: inip-discuss@ietfa.amsl.com
Delivered-To: inip-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DAF312D1D8 for <inip-discuss@ietfa.amsl.com>; Thu, 25 Aug 2016 09:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ainasystem-org.20150623.gappssmtp.com
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 DrTuh2SAI7AR for <inip-discuss@ietfa.amsl.com>; Thu, 25 Aug 2016 09:14:50 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDF0112D0FF for <inip-discuss@iab.org>; Thu, 25 Aug 2016 09:14:49 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id f65so245015281wmi.0 for <inip-discuss@iab.org>; Thu, 25 Aug 2016 09:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ainasystem-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=/4kNVprgjkJXFz/WXUppSqb0734rP/6iH/FqAJA9egg=; b=amV4SM7j6geZU5B3/ywhaHsWGUoZ33qdzbBHeD09FI44fLoz+dcC9YUI6x/YSncuIe 8lvXDH1U/E2zVJXkapOh0DEB98/L93VaTqdXHKi0yfDRPyQV9ZJ/2wws1lTu+HVtVe51 IshBf0OvCS+CMWjl45TgKMQlbd4Ibhiy1r+aKVjm6oW6uNCrPeSuGZfk+shWXOROIEnq 8oIlGap+8oznQK1/zbHLi5B0TLtWIYKylB4GoVKfdzK8Wd0MxkDORIXSKkiGLwH9iUJR GZ8VLCjYhmOmc4mQLczoCyb6xNk0mrIsmzKyRjFGNDWiZVdmRpQSmKxkTm3nVd+vZLW8 MWWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=/4kNVprgjkJXFz/WXUppSqb0734rP/6iH/FqAJA9egg=; b=miZfd7x18HfpqTk5TqRDPwnXcGogmjtal0vKbR3jKttOu9nCTtUcJoxN5JdPUL7+1Q 0yOflaB60iwpdkQQ4jNkBl0n+J3k+ngnLzZR5UK/XQyDYaif0cM8dI1dHPL2z11G7+bI FWSYcmKxy8QcpznPqCe/Q9A2/UshzAjXwPeWdkuSeHluY+IiSRYmEOMdTYNZSl0NQhS2 j4CY9Etn0nVU04IlV0TDTF6T1ksjjdCf2uvHwgPJTpw/4ygW+OlSxnBAChkOOWoa+BUv OeZPhKIB26y1CLOLbjjJBwsbPZ/9PTyX8+lK4GPJx3TaGu4GVwMjNZvdO6480ovk6vnR 56Lw==
X-Gm-Message-State: AEkoouu6+9r8/O2/PLVfS54xqaWNtG4ay3l/VTXiXq5Il6o/P0PQqM/bvJse2o1DPYUK8xZ5WU5rtGWEnVQkbg==
X-Received: by 10.194.113.105 with SMTP id ix9mr9301335wjb.30.1472141688072; Thu, 25 Aug 2016 09:14:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.74.219 with HTTP; Thu, 25 Aug 2016 09:14:47 -0700 (PDT)
Received: by 10.28.74.219 with HTTP; Thu, 25 Aug 2016 09:14:47 -0700 (PDT)
In-Reply-To: <CAOvDaJQfCpxhqc044Jrqxc6a8R6t6JyS9JSrS63Mbej5hE6K_w@mail.gmail.com>
References: <CAOvDaJRu5=03zhT5d=0USHmKc7zfmD89CwZ78QvJ=Lai4TAZ=Q@mail.gmail.com> <20160822233657.GL1712@mx2.yitter.info> <CAOvDaJS+K-8Shu5=z-qWB6PhhuFxHQ_M8V7wqSa14d1ANW1+xQ@mail.gmail.com> <20160823163553.GG17214@mx2.yitter.info> <CAOvDaJR_YuUqGeDfSQFQ_K_w9sj5TBaEb+Vrdf+Ughy0o+Abiw@mail.gmail.com> <F2C2544E-3DAE-40E0-8E5D-14EC95E3DDC4@viagenie.ca> <CAOvDaJQfCpxhqc044Jrqxc6a8R6t6JyS9JSrS63Mbej5hE6K_w@mail.gmail.com>
From: Bauyrzhan Askar <mail@ainasystem.org>
Date: Thu, 25 Aug 2016 17:14:47 +0100
Message-ID: <CAOvDaJTVt9jgcyp5xJy9ELN4nqOk8ZixTDb_UVia=SfZk-_zLQ@mail.gmail.com>
To: inip-discuss@iab.org
Content-Type: multipart/alternative; boundary="001a1130cef2608bf9053ae7b2b5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/inip-discuss/G7w-F2kplycXzqXxJnvXbFZ2-Qs>
Subject: Re: [Inip-discuss] Innovation in DNS
X-BeenThere: inip-discuss@iab.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IAB Internet Names and Identifiers Discussion List <inip-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/inip-discuss>, <mailto:inip-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/inip-discuss/>
List-Post: <mailto:inip-discuss@iab.org>
List-Help: <mailto:inip-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/inip-discuss>, <mailto:inip-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 16:14:52 -0000

Sorry Marc Blanchet

On 25 Aug 2016 17:13, "Bauyrzhan Askar" <mail@ainasystem.org> wrote:

> Thanks Mark
> I will investigate that RFC
> Best wishes
>
> On 25 Aug 2016 17:09, "Marc Blanchet" <marc.blanchet@viagenie.ca> wrote:
>
>> On 25 Aug 2016, at 12:01, Bauyrzhan Askar wrote:
>>
>> Hi there
>>
>> Unlike com zone, root zone is accessed every time when DNS resolution for
>> unknown domain name is requested no matter which TLD zone the unknown
>> domain name belongs to.
>>
>> Not true. That claim ignores the effects of TTLs.
>>
>> *So, increase of SLD together with TLD, increases rate of DNS resolution
>> query to root nameserver. *
>>
>> So?
>>
>> Andrew, would you explain the effects of TLL related to that claim.
>>
>> not wanting to respond for Andrew, but maybe he was referring to « TTL »
>> of negative caching (RFC2308, see section 5).
>>
>> Regards, Marc.
>>
>> For the purpose of clarification of the claim, TTL specifies time it will
>> be in cache of DNS resolver. I point you to “request to
>> *unknown domain name*” and it means that there is no record data for the
>> unknown domain
>> name not just on Internet users PC but also in DNS resolvers cache.
>>
>> As for the risk it brings, what kind of risk are you mentioning?
>> Cybersquatting, risk of switching to AINA System or other risks?
>>
>> I want to draw your attention to the part where implementation of the AINA
>> System is described. As you can see for the purpose of simplicity,
>> switching to AINA System can be conducted through three scenarios. (at
>> least three and it is up to imagination). The first one is the one which
>> has no risk, and what needed is just to direct requests to AINA System in
>> case of unknown domain name for root nameservers.
>>
>> Many problems may rise here not from the technical aspect but rather from
>> political or business interest aspects. And I hopefully believe that the
>> discussions conducted here is out of that topics.
>>
>> Thanks
>>
>> On Tue, Aug 23, 2016 at 5:35 PM, Andrew Sullivan ajs@anvilwalrusden.com
>> wrote:
>>
>> On Tue, Aug 23, 2016 at 05:24:21PM +0100, Bauyrzhan Askar wrote:
>>
>> Unlike com zone, root zone is accessed every time when DNS resolution for
>> unknown domain name is requested no matter which TLD zone the unknown
>> domain name belongs to.
>>
>> Not true. That claim ignores the effects of TTLs.
>>
>> *So, increase of SLD together with TLD, increases rate of DNS resolution
>> query to root nameserver. *
>>
>> So?
>>
>> But the problem here is that when TLD list increases and any entry or
>> update made to the root zone file in master root nameserver, all root
>> nameservers have to be updated which in turn
>>
>> 1) increases the load to network handling root nameservers. (this may
>> not be a big problem at the moment)
>>
>> 2) increases the time for update to be finished throughout the world
>> because of increased number of copies of root nameservers.
>>
>> 3) increases the load to any particular root nameserver, no matter of
>> number of copies of root nameserver, because of the increased rate of
>> updates.
>>
>> All of this is true of the com zone, too, so I don't see how it's
>> relevant at all. I just don't see that this is a significant
>> improvement of the DNS, and it involves adding changes to the system
>> that present their own risks. If we're going to undertake such risks,
>> it seems to me a tiny incremental improvement to address no actual
>> practical problem anyone has for only one zone seems like a low
>> return on the investment.
>>
>> Best regards,
>>
>> A
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>> ------------------------------
>>
>> Inip-discuss mailing list
>> Inip-discuss@iab.org
>> https://www.iab.org/mailman/listinfo/inip-discuss
>>
>> ------------------------------
>>
>> Inip-discuss mailing list
>> Inip-discuss@iab.org
>> https://www.iab.org/mailman/listinfo/inip-discuss
>>
>>