Re: [DNSOP] ALT-TLD and (insecure) delgations.

"Patrik Fältström " <paf@frobbit.se> Sat, 04 February 2017 08:05 UTC

Return-Path: <paf@frobbit.se>
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 C45E21293DF for <dnsop@ietfa.amsl.com>; Sat, 4 Feb 2017 00:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level:
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] 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 xs6DATEF5Z8c for <dnsop@ietfa.amsl.com>; Sat, 4 Feb 2017 00:05:05 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D3461293DC for <dnsop@ietf.org>; Sat, 4 Feb 2017 00:05:05 -0800 (PST)
Received: from [192.165.72.121] (unknown [IPv6:2a02:80:3ffc:0:59ec:5c38:18a5:a0c3]) by mail.frobbit.se (Postfix) with ESMTPSA id 9928A2352D; Sat, 4 Feb 2017 09:05:00 +0100 (CET)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Andrew Sullivan" <ajs@anvilwalrusden.com>
Date: Sat, 04 Feb 2017 09:05:00 +0100
Message-ID: <6CA33DCA-29B5-4BEF-8E9F-E93CE7115186@frobbit.se>
In-Reply-To: <20170204015722.GC67739@mx2.yitter.info>
References: <CAH1iCiqXohb_7LsQ2EMo8ZB-t20mKq_nUDS8vebhtSXoM13DTg@mail.gmail.com> <5FD13D0D-57DE-4CED-B1A2-C823079B8D63@gmail.com> <CAH1iCiqMhky7r-kaMFTa41b2ZBfd3Fiffp0Rknx_4moaBx3t6w@mail.gmail.com> <74796240-46DA-4C8B-A715-DBC521EFA3F3@gmail.com> <20170204015722.GC67739@mx2.yitter.info>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_CA5ECBA3-A276-4E11-8171-C6EA158F0692_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6076)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/a-JZNFJFGrtgQddvLmdaLZOetRA>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] ALT-TLD and (insecure) delgations.
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: Sat, 04 Feb 2017 08:05:06 -0000

On 4 Feb 2017, at 2:57, Andrew Sullivan wrote:

> On Fri, Feb 03, 2017 at 12:21:16PM -0800, Steve Crocker wrote:
>
>> And just to stir the pot a bit, what would you have ICANN do if someone applies for .alt as a top level domain?  Is it ok if we say yes and delegate the name?  If not, what is the basis for us to say no?
>
> If alt ends up in the 6761 special-use names registry, that seems a
> reason for ICANN not to delegate the name.  For adding something to
> the 6761 special-use names registry removes it from the possible pool
> of names that can be in the root zone.

This would be my suggestion.

What worries me is not names in 6761 special-use names registry but other names ICANN "should not" add to the root zone.

   paf