IETF Logo Mail Archive

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

Andrew Sullivan <ajs@anvilwalrusden.com> Sat, 04 February 2017 01:57 UTC

Return-Path: <ajs@anvilwalrusden.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 DF97D129579 for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 17:57:27 -0800 (PST)
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 SbpN2NRgtkKc for <dnsop@ietfa.amsl.com>; Fri, 3 Feb 2017 17:57:27 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id DF4FE127735 for <dnsop@ietf.org>; Fri, 3 Feb 2017 17:57:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 8AFC811649 for <dnsop@ietf.org>; Sat, 4 Feb 2017 01:57:30 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsEucxlCqNn7 for <dnsop@ietf.org>; Sat, 4 Feb 2017 01:57:30 +0000 (UTC)
Received: from mx2.yitter.info (192-0-220-231.cpe.teksavvy.com [192.0.220.231]) by mx2.yitter.info (Postfix) with ESMTPSA id DA10A1162D for <dnsop@ietf.org>; Sat, 4 Feb 2017 01:57:29 +0000 (UTC)
Date: Fri, 03 Feb 2017 20:57:22 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <74796240-46DA-4C8B-A715-DBC521EFA3F3@gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/VFeOZIe9NfintqZAaOtbNILP_h0>
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 01:57:28 -0000

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.

Best regards,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email