[DNSOP] Formal syntax in the Special-Use domain registry (Was: Alternative Special-Use TLD problem statement draft

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 07 April 2016 12:14 UTC

Return-Path: <bortzmeyer@nic.fr>
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 769F212D6DD for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 05:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 q5xUA1bIk_-G for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 05:14:17 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E07E512D6EB for <dnsop@ietf.org>; Thu, 7 Apr 2016 05:14:10 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 8E1A632838; Thu, 7 Apr 2016 14:14:08 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id D8F96F02B4E; Thu, 7 Apr 2016 14:13:46 +0200 (CEST)
Date: Thu, 07 Apr 2016 09:13:46 -0300
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: David Conrad <drc@virtualized.org>
Message-ID: <20160407121346.GA7424@laperouse.bortzmeyer.org>
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <m1anlSH-0000IqC@stereo.hq.phicoh.net> <20160406115243.GA14413@laperouse.bortzmeyer.org> <20160406122131.GA15698@laperouse.bortzmeyer.org> <A750F046-3B14-46C0-A815-DF481EB1B2E6@virtualized.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A750F046-3B14-46C0-A815-DF481EB1B2E6@virtualized.org>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 15.10 (wily)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/gmD8xAbi7aeOx4KhH7wFe2klrl4>
Cc: dnsop WG <dnsop@ietf.org>
Subject: [DNSOP] Formal syntax in the Special-Use domain registry (Was: Alternative Special-Use TLD problem statement draft
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: Thu, 07 Apr 2016 12:14:18 -0000

On Wed, Apr 06, 2016 at 09:51:03PM -0300,
 David Conrad <drc@virtualized.org> wrote 
 a message of 58 lines which said:

> > Some people complained that it was difficult enough with RFC 6761
> > (because there is no machine-readable version of the special-use
> > registry)
> 
> Last I looked
> http://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xml
> was XML and it's machine-readable.

No. Of course, its structure is machine-readable, but not the
contents, specially the rules about how DNS software should handle
this name. If you write a resolver and want to fully support RFC 6761,
you cannot write a script which will produce code (or configuration)
supporting the special rules, from the downloaded IANA registry. The
only solution is to read every RFC pointed by the registry, and then
update your code (or the default configuration).

It is funny that draft-adpkja-dnsop-special-names-problem spends a lot
of time in political rants and seldom mentions this very practical
limit of RFC 6761.

Addressing it (6761-bis?) won't be easy because it means developing a
limited set of possible policies for special-use names.

> Put special use registry be put into the DNS, e.g.,

No, same problem.