Re: [Inip-discuss] Innovation in DNS

Bauyrzhan Askar <mail@ainasystem.org> Thu, 25 August 2016 16:13 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 8012912D858 for <inip-discuss@ietfa.amsl.com>; Thu, 25 Aug 2016 09:13:23 -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 xa9koV1OJRsT for <inip-discuss@ietfa.amsl.com>; Thu, 25 Aug 2016 09:13:15 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 6EDFE12D825 for <inip-discuss@iab.org>; Thu, 25 Aug 2016 09:13:14 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id f65so244958981wmi.0 for <inip-discuss@iab.org>; Thu, 25 Aug 2016 09:13:14 -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=pcV8/dSb9CzJXFl6vvTFG2DXO+pnu31nPPvD2PSsq70=; b=cg7cr8iyngcFJ7j2dmbMMrJJJJnS3f/GkShKOwGesOylZTJFJqnZ+ldvzg2Kb5aHpw xsZiGyHxzp+k0qR4atVy2xMhth4apzwb8aCydavIy3kDE/Q/5zsgTqy5/WPajW74j3QC DRHjjsMw8VVJoErgOd651cWqpH3zDVTdbvEd7i4rFmPLgPNBldDZKlNYvpN5Kb3xhJxJ h6jJJvJB8mRGC+R8ibq13TjYqE71JLP+ufY0+GMA6Le7Ac6/68UYb1J2dFPyoDXkuGkp Md2NoLRTMe2GqU3lqMWITl0oxM/KtzdxEcDI41NoP/clxVJ02gdujOZmA0o+ri0C262x y6rA==
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=pcV8/dSb9CzJXFl6vvTFG2DXO+pnu31nPPvD2PSsq70=; b=S5LBRyXc4W9ISbO/UGP6Su+R8dzpzBGOf9xgvQAoT6Vl0qjt1pItnEDvUneSMwxgvu WHNW619RKrwUMi2ptKXIILgU/ug4A3ItbXtyydIOdm7MSmjuBkudUOnr8ANmIN9sH6QM 8ZOrZSn/Mi84MU0hQwgmqqCLBK06ty3t7cr7wqmbFnTuGWqgNM3pGkjhDKLCF1qWiclz cxa9bzAVJVc2QLo4+APv0QR/zCR5DQvDNif7r9JxSCPh5KrorbcvchQbyzwozkq/TvYf k83V4skXp8ifiAAiLhPWByOmoeG4/t2cyoYo9rV4f/+gTwir7RSyKP4RfaGsX+0dmINU dggw==
X-Gm-Message-State: AEkoouuNMvKx6oAv3a/sIrp6vSU56M9zuaiIpLItdzwnGuSb/G+Bsbkt3Hn7buG4TvbHzQJtSvCZOPyBGBFgIg==
X-Received: by 10.28.132.195 with SMTP id g186mr22536952wmd.108.1472141592657; Thu, 25 Aug 2016 09:13:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.74.219 with HTTP; Thu, 25 Aug 2016 09:13:12 -0700 (PDT)
Received: by 10.28.74.219 with HTTP; Thu, 25 Aug 2016 09:13:12 -0700 (PDT)
In-Reply-To: <F2C2544E-3DAE-40E0-8E5D-14EC95E3DDC4@viagenie.ca>
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>
From: Bauyrzhan Askar <mail@ainasystem.org>
Date: Thu, 25 Aug 2016 17:13:12 +0100
Message-ID: <CAOvDaJQfCpxhqc044Jrqxc6a8R6t6JyS9JSrS63Mbej5hE6K_w@mail.gmail.com>
To: inip-discuss@iab.org
Content-Type: multipart/alternative; boundary="001a11442206b0d7f4053ae7ac81"
Archived-At: <https://mailarchive.ietf.org/arch/msg/inip-discuss/S4sM0KeUtbjSOFJsPLAD5ty0oxk>
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:13:23 -0000

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
>
>