[Bundled-domain-names] Bundles in practice
"John R Levine" <johnl@taugh.com> Fri, 05 February 2016 03:01 UTC
Return-Path: <johnl@taugh.com>
X-Original-To: bundled-domain-names@ietfa.amsl.com
Delivered-To: bundled-domain-names@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719B41B30B6 for <bundled-domain-names@ietfa.amsl.com>; Thu, 4 Feb 2016 19:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.136
X-Spam-Level:
X-Spam-Status: No, score=-3.136 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, KHOP_DYNAMIC=0.001, SPF_PASS=-0.001] autolearn=ham
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 Xn9tC_LfRah8 for <bundled-domain-names@ietfa.amsl.com>; Thu, 4 Feb 2016 19:01:54 -0800 (PST)
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-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BEB31B3012 for <bundled-domain-names@ietf.org>; Thu, 4 Feb 2016 19:01:51 -0800 (PST)
Received: (qmail 72222 invoked from network); 5 Feb 2016 03:01:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=11a1d.56b4109e.k1602; bh=izFVKzC8ADx3bhWjgZn1oEj5CJfHK3RoV0G4FRrESHc=; b=jz/v2AmgP++HPDqC1JwR33ZW5vNjBaNuoKGb5f7yRd6F64I8cnA898Z/duSTkBUdGmbqzLZlcKCsivBOZbpHVfyXsjwJD8vd2oArTnVKFD/Mt7sz4ZqsNBeUC5b3FFkcnwAaKXBtlDfniC5Q3X7BJfVVKgGdzsfccgNHbSjgwsPfO6KkMy682WHMmzl+EBFQYDQjeKwlykiNfj594o7gDGPNRAjJQXkoizhDrHiwLVr8QxJLul9cRGm6MA1Yo0YH
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=11a1d.56b4109e.k1602; bh=izFVKzC8ADx3bhWjgZn1oEj5CJfHK3RoV0G4FRrESHc=; b=t7JIUNzNKOxwFT54AWxgdXG0S6HGd9dKF4iChCOZuvdHiEfbtaZzaonRiDu4fN3DTsB19HKp4Sdm/4OZqwAQDS8DEiw+BhcUOjNuBkIWzXPq8yrpH0L69lnjV4pfh1l42vs3NYXwKpjCD7w5xYz1Z0ojUPMN0ePxn5hC399gydbJyOVGgq7maxKg2kydg9dZS8xZfRUdKAMks0FPJGP3dhaju+vrP1oT4DLnel2D/v2AhlNVXGyaQpMYU2YqZKJX
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 05 Feb 2016 03:01:50 -0000
Date: Thu, 04 Feb 2016 22:01:49 -0500
Message-ID: <alpine.OSX.2.11.1602042200280.74409@ary.lan>
From: John R Levine <johnl@taugh.com>
To: bundled-domain-names@ietf.org
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-2017876425-1454641310=:74409"
Archived-At: <http://mailarchive.ietf.org/arch/msg/bundled-domain-names/bEVvxw_uxIb13HqN1vR-IDN95_M>
Subject: [Bundled-domain-names] Bundles in practice
X-BeenThere: bundled-domain-names@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of \"bundled domain names\"" <bundled-domain-names.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bundled-domain-names>, <mailto:bundled-domain-names-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bundled-domain-names/>
List-Post: <mailto:bundled-domain-names@ietf.org>
List-Help: <mailto:bundled-domain-names-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bundled-domain-names>, <mailto:bundled-domain-names-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 03:01:56 -0000
I admire the bravery of those of you who jumped into the name bundling swamp. It might be useful to identify some places where various approaches to bundling are in use now, since it could give us some hints about how well it works. Here's some we found in and since RFC 6927. * DNAME at 2LD This is used in .CAT and I think .GR. In .CAT, they bundle accented and unaccented letters, so if you register exámple.cat, you also get example.cat, and they add a dname: exámple.cat. DNAME example.cat. Having looked at it, I can say this works very badly. For one thing, since DNAME only affects descendant names, www.exámple.cat is defined, but plain exámple.cat is not which among other things means that email doesn't work. I spot checked a bunch of .cat web site and found that almost without exception, web servers just provision the unaccented name and the accented one gives you an error or a default page. * DNAME at TLD Taiwan makes the simplified character version of its Chinese name a DNAME for the traditional version: xn--kprw13d. 86400 IN DNAME xn--kpry57d. This avoids the missing 2LD problems that .CAT has, but I don't read Chinese so I don't know how well it works in practice. * Parallel name servers PIR's new .NGO and .ONG domains are always paired, so if you register a name in one, you get the same name in the other pointing at the same name servers. I've registered a name in .NGO and so far the most notable thing I've discovered is that getting DNSSEC DS records provisioned is really painful. Your record at your registrar just shows the version you registered, so to do the other one needs some ill-defined kludge. (Actually, my registrar can't do DNSSEC at all for .NGO, but I hear the kludge is coming.) Other than that it's straightforward to configure the DNS, but of course it's up to me to decide how similar I want the two zones to be. R's, John
- [Bundled-domain-names] Bundles in practice John R Levine