Re: [dnsext] Increasing character limit for registration in internet domain names: 76 or 68 or 91 or 83 or 64 higher the better

Florian Weimer <fweimer@bfk.de> Tue, 18 January 2011 14:53 UTC

Return-Path: <fweimer@bfk.de>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE3FD28C141 for <dnsext@core3.amsl.com>; Tue, 18 Jan 2011 06:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.131
X-Spam-Level:
X-Spam-Status: No, score=-2.131 tagged_above=-999 required=5 tests=[AWL=0.118, 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 nSR5Jf-pBiiW for <dnsext@core3.amsl.com>; Tue, 18 Jan 2011 06:53:00 -0800 (PST)
Received: from mx01.bfk.de (mx01.bfk.de [193.227.124.2]) by core3.amsl.com (Postfix) with ESMTP id A199528C13A for <dnsext@ietf.org>; Tue, 18 Jan 2011 06:52:59 -0800 (PST)
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1PfCy7-0000Xl-JN for dnsext@ietf.org; Tue, 18 Jan 2011 14:55:35 +0000
Received: by bfk.de with local id 1PfCy7-00012k-Ag for dnsext@ietf.org; Tue, 18 Jan 2011 14:55:35 +0000
To: dnsext@ietf.org
References: <AANLkTikv9muqBKbm0WpvtkyFb5DT9==P_6ySAow7u0b7@mail.gmail.com> <82ei8afq4p.fsf@mid.bfk.de> <85987.1295361055@nsa.vix.com>
From: Florian Weimer <fweimer@bfk.de>
Date: Tue, 18 Jan 2011 14:55:35 +0000
In-Reply-To: <85987.1295361055@nsa.vix.com> (Paul Vixie's message of "Tue\, 18 Jan 2011 14\:30\:55 +0000")
Message-ID: <82y66iclco.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dnsext] Increasing character limit for registration in internet domain names: 76 or 68 or 91 or 83 or 64 higher the better
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 14:53:01 -0000

* Paul Vixie:

>> From: Florian Weimer <fweimer@bfk.de>
>> Date: Tue, 18 Jan 2011 10:44:06 +0000
>> 
>> I wasn't really around when the failure of this experiment was
>> recognized.  Is there a write-up somewhere explaining why this doesn't
>> work as expected?  (Without major protocol surgery, increasing the
>> label length would share a similar fate.)
>
> no writeup. briefly, it only works if the full end-to-end path knows
> about each new label type. so adding each label type would require 
> incrementing the EDNS version number. this was found to be impractical.

And "full path" has two meanings here, both the forwarders to the
authoritative server, and the delegation path from the root to the
authoritative servers.  If no server is known for a particular
subtree, the full QNAME is sent to the roots, then to the applicable
TLD servers etc., so all your parents need to support such an
extension before you can use it in your zone.

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99