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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Thu, 07 April 2016 12:39 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 9C5F512D86B for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 05:39:42 -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 n7oFOg8zbaBs for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 05:39:41 -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 D704112D515 for <dnsop@ietf.org>; Thu, 7 Apr 2016 05:39:40 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 42C8E32838; Thu, 7 Apr 2016 14:39:39 +0200 (CEST)
Received: by tyrion (Postfix, from userid 1000) id 8E9E3F02B4E; Thu, 7 Apr 2016 14:35:32 +0200 (CEST)
Date: Thu, 07 Apr 2016 09:35:32 -0300
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Adrien de Croy <adrien@qbik.com>
Message-ID: <20160407123532.GA9730@laperouse.bortzmeyer.org>
References: <m1anp1K-0000CzC@stereo.hq.phicoh.net> <em11200959-d7c7-42af-95ce-93dfe4d4b0a9@bodybag>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <em11200959-d7c7-42af-95ce-93dfe4d4b0a9@bodybag>
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/ZZnKM4cvU-EuKDvkZeWOpyQ9EjM>
Cc: Philip Homburg <pch-dnsop@u-1.phicoh.com>, "dnsop@ietf.org" <dnsop@ietf.org>
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: Thu, 07 Apr 2016 12:39:42 -0000

On Wed, Apr 06, 2016 at 08:48:19PM +0000,
 Adrien de Croy <adrien@qbik.com> wrote 
 a message of 73 lines which said:

> so therefore the DNS namespace has to be perverted.

>From the discussion at the IETF plenary yesterday evening, I got the
feeling that IETF 100 in Singapore will be clean of perversions :-)

> And when I see arguments like the IETF should assign root names so
> that organisations who can't afford lawyers

Such organisations should not be allowed to exist, I agree.

> I think the security implications of a resolver checking some
> internet source for a machine readable list of the latest special
> use names have not even been considered,

There is today, unfortunately, no such list. Should it exist in
6761-bis, I'm fairly certain the authors would add in the Security
Considerations section that the list must be authenticated (for
instance HTTPS to IANA with a thorough certificate check). It is not
different than the retrieval of the DNS root key.