IETF Logo Mail Archive

Re: [DNSOP] Special-use TLDs in resolvers

Steve Crocker <steve@shinkuro.com> Fri, 16 August 2019 15:59 UTC

Return-Path: <steve@shinkuro.com>
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 172C8120869 for <dnsop@ietfa.amsl.com>; Fri, 16 Aug 2019 08:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=shinkuro-com.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 IqW6GkEjtBBG for <dnsop@ietfa.amsl.com>; Fri, 16 Aug 2019 08:59:41 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 30A6D120828 for <dnsop@ietf.org>; Fri, 16 Aug 2019 08:59:41 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id h8so2108555ybq.9 for <dnsop@ietf.org>; Fri, 16 Aug 2019 08:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shinkuro-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=asXuSoNCA7lA3u/VA1Fia+U6uMwDAmIPPbXey+AT/LQ=; b=QOhItzuqntlFUBw0oBWaC7g0G5yweNRVNi+SLfnNL0pwCBXkiPi2xUseyMYdqxh8ie flg0O7xvxPmhkNKjC/J4am/mSms0Spv2OsS9WNhkNxLiH7BsYyZQV4vhn1JYn3GqC3C9 z6mylYj9keyqBs4CmB2JqttiS4Yv3ClXkDhpbSlJmE9ApVnw85steZESK39gh7Nwhpgq yOzTfUIlbger+g+CJKtP0tjNFgQ9Y8qVnB/nCl7t7n1h+3Y9IT+iqURAF6RKtLDj0TpM orLv5mLckRmGSAjdKyStRNzOsF4bkvtvDXTxqDkHQ30QmUnnEzbVKGoqctR+fkl6bget 1dMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=asXuSoNCA7lA3u/VA1Fia+U6uMwDAmIPPbXey+AT/LQ=; b=nlQ5YpISP+OiewoU4yaKJ9jhZOJh/CsCUHsL8teVRTIM3QDLGYl+nwiqbWib+sbV3S 0j6PYhmmEFP2CL1gjtEHE/l85GSn8/zvsJdIk1J7RbU4e2jGcDHO+2kC2dsdYhyqjNak xyKM3sAzRP9q+L1nUCd94zLYA6B4rdgtS9d0RQd7HqaUcgM2BbH5SRAzWl9zax9R7NuR Ig5vTAUFKuWpUjIIu542xLuuiYxNV6ecKXlIwyyg8Axmr6dBz9LDpkMvPhefJsuXES1l NVjShNENIGECFigqDjy9E6dgPmcILK3jfesH5PlCO6Te3ApLL+AwPQM4KkHf4GkIz8Da JFEw==
X-Gm-Message-State: APjAAAWtBacHlwMc2tJciirTM9TGDxsI0Us3TOg7Q46HPyWi2Pz//Wjc TD5mbj4hAikCbTZtBIKucEAcpWK7X0tEu2ElI2F25A==
X-Google-Smtp-Source: APXvYqzNvUa82DFP8TbSbhU8dfhjLSziWasRyZML8dM8p1oBskb86yy7bflX4IswzRCOLlgp1e+xDnefYvh3Ksly9B8=
X-Received: by 2002:a05:6902:52e:: with SMTP id y14mr7730394ybs.272.1565971180250; Fri, 16 Aug 2019 08:59:40 -0700 (PDT)
MIME-Version: 1.0
References: <a6f528a1-01d0-3bd5-1a7f-96ff4e9bcd85@nic.cz> <20190816144655.jxd37dwn2t4ywuko@mx4.yitter.info> <CABf5zv+cCrQxCeOC1qsijSpujZYqhOB0EuzrTbG+yEX6we0jpQ@mail.gmail.com> <DE6E82A3-A610-4339-970E-876C5CE4727E@hopcount.ca>
In-Reply-To: <DE6E82A3-A610-4339-970E-876C5CE4727E@hopcount.ca>
From: Steve Crocker <steve@shinkuro.com>
Date: Fri, 16 Aug 2019 11:59:29 -0400
Message-ID: <CABf5zvLFJhtoyiHbmBheuEBN==LKg1b97uv7efVVMCHMA4AuUQ@mail.gmail.com>
To: Joe Abley <jabley@hopcount.ca>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ed7e2905903e1328"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/i_qmCDmJwDEhCCiTcA6R1l97IZs>
Subject: Re: [DNSOP] Special-use TLDs in resolvers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 16 Aug 2019 15:59:49 -0000

Ack.  Tnx.

On Fri, Aug 16, 2019 at 11:56 AM Joe Abley <jabley@hopcount.ca> wrote:

> On 16 Aug 2019, at 10:59, Steve Crocker <steve@shinkuro.com> wrote:
>
> > At the risk of revealing that I haven't been following this thread
> carefully, I don't understand how a resolver is supposed to know all of the
> special names.  Resolvers that are configured to know that invalid, local,
> onion, and test are special will not know about the next name that's put on
> the special list.
>
> The pragmatic answer right now is that vendors and package maintainers do
> a good job with their default configurations. DNS software tends to get
> upgraded frequently enough in applications with significant user bases that
> this goes some of the distance.
>
> I can see your point though that there might be some merit in having a way
> to retrieve a current list, or at least telling whether the list you have
> is up-to-date. I don't know that I think it's a particularly pressing
> problem though (I think DNSSEC trust anchor distribution for the root zone
> is higher up the priority list, for example).
>
>
> Joe
>

v2.23.0 | Report a Bug | By Email