Re: [DNSOP] Services and top-level DNS names

Florian Weimer <fw@deneb.enyo.de> Mon, 07 July 2008 02:11 UTC

Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: dnsop-archive@lists.ietf.org
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 991423A69C1; Sun, 6 Jul 2008 19:11:09 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40BE3A69B5 for <dnsop@core3.amsl.com>; Sun, 6 Jul 2008 19:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sj4TeomdWqqG for <dnsop@core3.amsl.com>; Sun, 6 Jul 2008 19:11:08 -0700 (PDT)
Received: from mail.enyo.de (mail.enyo.de [IPv6:2001:14b0:202:1::a7]) by core3.amsl.com (Postfix) with ESMTP id 1D4903A6957 for <dnsop@ietf.org>; Sun, 6 Jul 2008 19:11:07 -0700 (PDT)
Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de) by mail.enyo.de with esmtp id 1KFgC4-000719-Bk; Mon, 07 Jul 2008 04:11:08 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.69) (envelope-from <fw@deneb.enyo.de>) id 1KFgC3-0006er-SY; Mon, 07 Jul 2008 04:11:07 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: Andras Salamon <andras@dns.net>
References: <200807050409.m6549KdD062463@drugs.dv.isc.org> <486F0288.4040909@ca.afilias.info> <20080707010014.GA1893@dns.net>
Date: Mon, 07 Jul 2008 04:11:07 +0200
In-Reply-To: <20080707010014.GA1893@dns.net> (Andras Salamon's message of "Mon, 7 Jul 2008 02:00:14 +0100")
Message-ID: <87k5fymojo.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Services and top-level DNS names
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org

* Andras Salamon:

>    ftp://ftp.rfc-editor.org/in-notes/rfc1535.txt

Have you noticed that this document calls for the implementation of a
public suffix lis? 8-)

> I routinely dot-terminate domain names and disable search lists,

This doesn't work reliably with HTTP as deployed, by the way.

I don't see the problem with a static, non-devolving search list which
is always tried first.  Sure, there is a collision if certain TLDs are
introduced, but at least it's backwards-compatible.  But it's
unreasonable to assume that just because you paid ICANN a certain amount
of money, your shiny new TLD is globally usable--single root or not.  It
doesn't work that way with IP addresses, where considerably less
politics are involved, so I don't see why DNS should be any better.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop