[dnsext] How DNAME solves the aliasing problem in Unicode for ITU-T/ISO OIDs

Alfred Hönes <ah@TR-Sys.de> Wed, 22 September 2010 19:23 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3103E3A6A7D; Wed, 22 Sep 2010 12:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.605
X-Spam-Level:
X-Spam-Status: No, score=-97.605 tagged_above=-999 required=5 tests=[AWL=0.544, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 yoS6vad5yS12; Wed, 22 Sep 2010 12:23:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 92F7C3A6A70; Wed, 22 Sep 2010 12:23:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OyUnW-00080E-UP for namedroppers-data0@psg.com; Wed, 22 Sep 2010 19:16:06 +0000
Received: from gateway.tr-sys.de ([213.178.172.147] helo=TR-Sys.de) by psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <A.Hoenes@TR-Sys.de>) id 1OyUnR-0007zJ-Fe for namedroppers@ops.ietf.org; Wed, 22 Sep 2010 19:16:02 +0000
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA206722806; Wed, 22 Sep 2010 21:13:26 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA26584; Wed, 22 Sep 2010 21:13:26 +0200 (MESZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201009221913.VAA26584@TR-Sys.de>
Subject: [dnsext] How DNAME solves the aliasing problem in Unicode for ITU-T/ISO OIDs
To: namedroppers@ops.ietf.org
Date: Wed, 22 Sep 2010 21:13:25 +0200 (MESZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

Folks,
I eventually was able to follow up to an ITU-T liaison
statement [1] that Patrick has brought to the attention of
the apps-discuss list [2] shortly before IETF in Maastricht.

You might know that a joint ITU-T / ISO effort has created a new
hierarchical OID system based on Unicode / UTF-8 labels:
ITU-T X.660 | ISO/IEC 9834.  They also have filed with IANA
a provisional 'oid' URI Scheme registration for this system, based
on an I-D [3] not (yet) accepted by the IESG for publication [4].

In the liaison statement, a draft version of ITU-T X.672 has been
provided for comment to the IETF -- it is available from [1].

The draft X.672 specifies a DNS/NAPTR based basic resolution system
("ORS") for OIDs with an extensible set of services, operating in the
".oid-res.org" DNS tree in a similar manner as the reverse DNS trees
for IPv4 and IPv6 are organized.
For the benefit of users (and the cash flow of OID registration
authorities?), the 'new' OID system allows unlimited registering
of aliases at each level of the tree (not even restricted to
'sibling' OIDs in the OID tree).

Therefore, it is interesting to observe how the ITU-T and ISO/IEC
deal with the aliasing problem in the OID system and in the ORS.

Please refer to the above draft recommendation and the references
listed therein for details.

In essence:
The ITU-T recognizes the necessity of primary (canonical) OIDs and
OID labels (and hence, if you want to use these terms, the existence
of "first-class" and "second-class" citizens / OIDs), and they
specify the use of DNAME in the delegating zone and simply prohibit
the necessity for non-structural RRs at such delegation points by
requiring an additional, service-specific label for all
'information-carrying' RRs (NAPTRs, so far, but new ORS applications
might involve other RR types).
(Translated to the HTTP world, the equivalent method would be to
mandate (e.g.) "www." in front of zone names with A/AAAA RRs for
web servers.)
This way, the ITU-T has no need for CNAME+DNAME, BNAME, etc.,
and no provisioning issues!  The resolution system always returns
the RRset at the canonical name.

Transfering this solution to the IDNA TLD and sub-TLD alias
registration problem, the solution would be to perform "delegation"
of all IDNA aliases via DNAME RRs in the 'registrating' zone
(e.g., root zone for TLD aliases) and to mandate the non-use of other,
information-carrying RR types at these "alias delegation points".
Registrants would be recommended to use simple, universal sub-domain
names for such aliased domains, which would not be subject to I18N
and the alias problem; the canonical names' DNS nodes of course would
be allowed to hold any information-carrying RRs.

Observing that ISO/IEC and ITU-T apparently can 'live' with this
method (and do that without an outstanding controversy!), I'm asking
myself why ICANN and the TLD registries would not be able do operate
with such methods.


Kind regards,
  Alfred Hönes.


BTW: I have filed comments on the draft [5], partly DNS related.
     Thus, you don't need to complain about the same issues again.

[1]
 https://datatracker.ietf.org/liaison/903/
[2]
 http://www.IETF.ORG/mail-archive/web/apps-discuss/current/msg01613.html
[3]
 http://tools.IETF.ORG/html/draft-larmouth-oid-iri-04
[4]
 https://datatracker.IETF.ORG/doc/draft-larmouth-oid-iri/
[5]
 http://www.IETF.ORG/mail-archive/web/apps-discuss/current/msg01782.html

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+