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

"Adrien de Croy" <adrien@qbik.com> Thu, 07 April 2016 20:36 UTC

Return-Path: <adrien@qbik.com>
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 4FCBD12D6BD for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 13:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 fJZQGX4G2R7q for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2016 13:36:35 -0700 (PDT)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (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 E109C12D65D for <dnsop@ietf.org>; Thu, 7 Apr 2016 13:36:34 -0700 (PDT)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v8.5.6 (Build 4877)) with SMTP id <0000693535@smtp.qbik.com>; Fri, 08 Apr 2016 08:36:32 +1200
From: Adrien de Croy <adrien@qbik.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date: Thu, 07 Apr 2016 20:36:32 +0000
Message-Id: <em7051f390-7149-4515-b21d-e8deec5bf49a@bodybag>
In-Reply-To: <20160407123532.GA9730@laperouse.bortzmeyer.org>
User-Agent: eM_Client/6.0.24928.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/2jdy1cBRHNY7mv-gBtnPkYFm8mg>
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
Reply-To: Adrien de Croy <adrien@qbik.com>
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 20:36:37 -0000


------ Original Message ------
From: "Stephane Bortzmeyer" <bortzmeyer@nic.fr>
To: "Adrien de Croy" <adrien@qbik.com>
Cc: "Philip Homburg" <pch-dnsop@u-1.phicoh.com>; "dnsop@ietf.org" 
<dnsop@ietf.org>
Sent: 8/04/2016 12:35:32 a.m.
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft

>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 didn't say or imply that - only that they should not be privileged 
compared with everyone else when it comes to getting names reserved in 
the domain name space.


>
>>  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.
And maybe it will be the first protocol ever to not suffer from 
unexpected security consequences.

Adrien

>
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop