Re: [Inip-discuss] Innovation in DNS
"Marc Blanchet" <marc.blanchet@viagenie.ca> Thu, 25 August 2016 16:09 UTC
Return-Path: <marc.blanchet@viagenie.ca>
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 A60CC12D7CB for <inip-discuss@ietfa.amsl.com>; Thu, 25 Aug 2016 09:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 9zqYWy1BX65u for <inip-discuss@ietfa.amsl.com>; Thu, 25 Aug 2016 09:09:36 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A918812D1DD for <inip-discuss@iab.org>; Thu, 25 Aug 2016 09:09:36 -0700 (PDT)
Received: from [10.0.1.45] (h126.viagenie.ca [206.123.31.126]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1AEE04759B; Thu, 25 Aug 2016 12:09:36 -0400 (EDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: Bauyrzhan Askar <mail@ainasystem.org>
Date: Thu, 25 Aug 2016 12:09:35 -0400
Message-ID: <F2C2544E-3DAE-40E0-8E5D-14EC95E3DDC4@viagenie.ca>
In-Reply-To: <CAOvDaJR_YuUqGeDfSQFQ_K_w9sj5TBaEb+Vrdf+Ughy0o+Abiw@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>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_C7365FAE-CA4F-471C-B8E8-198E55506D9F_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/inip-discuss/uNpwdKbpGnoOVjSYxnNSBiz9x80>
Cc: inip-discuss@iab.org
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:09:38 -0000
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
- [Inip-discuss] Innovation in DNS Bauyrzhan Askar
- Re: [Inip-discuss] Innovation in DNS Scott Weeks
- Re: [Inip-discuss] Innovation in DNS Andrew Sullivan
- Re: [Inip-discuss] Innovation in DNS Scott Weeks
- Re: [Inip-discuss] Innovation in DNS Andrew Sullivan
- Re: [Inip-discuss] Innovation in DNS Bauyrzhan Askar
- Re: [Inip-discuss] Innovation in DNS Andrew Sullivan
- Re: [Inip-discuss] Innovation in DNS Bauyrzhan Askar
- Re: [Inip-discuss] Innovation in DNS Marc Blanchet
- Re: [Inip-discuss] Innovation in DNS Bauyrzhan Askar
- Re: [Inip-discuss] Innovation in DNS Bauyrzhan Askar
- Re: [Inip-discuss] Innovation in DNS Andrew Sullivan
- Re: [Inip-discuss] Innovation in DNS Suzanne Woolf