IETF Logo Mail Archive

Re: [DNSOP] Alternative Special-Use TLD problem statement draft

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 06 April 2016 12:21 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 D93F812D5A8 for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 05:21:46 -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 gTK8ASfM4u3W for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 05:21:44 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (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 8813012D512 for <dnsop@ietf.org>; Wed, 6 Apr 2016 05:21:44 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id EBAAB3283E; Wed, 6 Apr 2016 14:21:42 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id A0341F008AD; Wed, 6 Apr 2016 14:21:31 +0200 (CEST)
Date: Wed, 06 Apr 2016 09:21:31 -0300
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Philip Homburg <pch-dnsop@u-1.phicoh.com>
Message-ID: <20160406122131.GA15698@laperouse.bortzmeyer.org>
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <m1anlSH-0000IqC@stereo.hq.phicoh.net> <20160406115243.GA14413@laperouse.bortzmeyer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160406115243.GA14413@laperouse.bortzmeyer.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/zbctXk1zjGWMrS7OoXR7AN8Tp7o>
Cc: dnsop@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [DNSOP] 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: Wed, 06 Apr 2016 12:21:47 -0000

On Wed, Apr 06, 2016 at 08:52:43AM -0300,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 21 lines which said:

> > So anybody who wants to play with an experimental naming service can just
> > register my-naming-service.net. And use that string in any name switch code.
> 
> Strong dissensus here. The problem is there is no safe way to have AND
> KEEP such a name.

Also, it would make very difficult to DNS programmers to keep track of
all these "special but not special" domain names. Some people
complained that it was difficult enough with RFC 6761 (because there
is no machine-readable version of the special-use registry) but it
would be worse with scattered domain names in many TLDs.

v2.23.0 | Report a Bug | By Email