Re: [DNSOP] moving forward on special use names

"John Levine" <johnl@taugh.com> Sun, 18 September 2016 21:10 UTC

Return-Path: <johnl@taugh.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 1342112B10A for <dnsop@ietfa.amsl.com>; Sun, 18 Sep 2016 14:10:53 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 w0iMHfHBdbm4 for <dnsop@ietfa.amsl.com>; Sun, 18 Sep 2016 14:10:51 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7305712B0E0 for <dnsop@ietf.org>; Sun, 18 Sep 2016 14:10:51 -0700 (PDT)
Received: (qmail 52317 invoked from network); 18 Sep 2016 21:10:48 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 18 Sep 2016 21:10:48 -0000
Date: 18 Sep 2016 21:10:28 -0000
Message-ID: <20160918211028.78666.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <8f5eb481-c8e9-cdbe-a9d1-3390053c5c13@acm.org>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6PFXlpqQ3zAcqKqV61K98tBEOTQ>
Subject: Re: [DNSOP] moving forward on special use names
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: Sun, 18 Sep 2016 21:10:53 -0000

>On 12-Sep-16 16:19, Suzanne Woolf wrote:
>> It seems unlikely that they can be combined, so we simply have to ask
>> the WG to choose.

The more I think about it, the more I think that they're both too
long, and we'd be better off with a one or two sentence description of
what we're trying to do, perhaps along these lines:

  * Describe how and when to recognize domain names that are handled
  in ways other than the DNS.  (That's mDNS and .onion)

or

  * Describe how and when to recognize domain names that should not
  be delegated in the DNS. (That's the toxic waste.)

or maybe something else, so long as it's short.


Also, FYI:

>> 4.2.4. Name Collision in the DNS ...

>This study is from before the new gTLD program.  The assumption in the
>report need to be tested against what actually happened in the round of
>new gTLDs before it can be included as part of the fact basis for this
>work.  We also need information on the degree of success that the
>various mitigation strategies had in overcoming possible problems to
>have a full picture of the problem as it has been shown in practice.

At a meeting a couple of weeks ago, I believe that someone said that
the junk traffic at the roots for each of .corp, .home and .mail still
greatly exceeds all of the traffic for the new gTLDs.  So I think it's
safe to say none of the mitigation strategies have worked.

The wildcard 127.0.53.53 and such are clever, but none of the domains
that have been delegated had significant collision issues to start
with so it's hard to argue they've been effective.

R's,
John