IETF Logo Mail Archive

Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt

Jim Reid <jim@rfc1035.com> Tue, 04 February 2014 08:22 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0EF1A039B for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 00:22:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
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 81Q2hjDkGVMb for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 00:22:56 -0800 (PST)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) by ietfa.amsl.com (Postfix) with ESMTP id B9E421A018E for <dnsop@ietf.org>; Tue, 4 Feb 2014 00:22:56 -0800 (PST)
Received: from [158.38.10.162] (unknown [158.38.10.162]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 93AD32420FA3; Tue, 4 Feb 2014 08:22:55 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20140204012148.GE16180@mx1.yitter.info>
Date: Tue, 04 Feb 2014 08:22:54 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBEC374F-F6B9-4BEC-B3B5-5A8E4045ED66@rfc1035.com>
References: <20140130004530.C660CE086E0@rock.dv.isc.org> <20140203151958.GA1673@nic.fr> <6BE00F1A-1F8D-4B30-A5C7-10E7466109C2@vpnc.org> <ACF06352-98E5-4368-A8C9-5AB50783C2D3@hopcount.ca> <20140203212333.1259EE44493@rock.dv.isc.org> <CF15D98C.197C0B%jonne.soininen@renesasmobile.com> <CAKr6gn1dpWz3LP9bpA2JebRDSN7GeOW65+Q1tW_dv=9KzgZaCQ@mail.gmail.com> <A6D7CE2E-BF9C-4077-A571-0C455E5DAE1F@nominum.com> <CAKr6gn08xayJCK_GtGNeYbet6tD=GwPJoSYL3tbRXomfxckHWA@mail.gmail.com> <ED2AE016-766D-41DE-A428-DEC49A350E8C@nominum.com> <20140204012148.GE16180@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1510)
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] additional special names Fwd: I-D Action: draft-chapin-additional-reserved-tlds-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 04 Feb 2014 08:22:59 -0000

On 4 Feb 2014, at 01:21, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

>    If you want to use a name in DNS protocol slots, then you need a DNS
>    name.  You didn't get a DNS name, and instead you used a label
>    that wasn't under your control.  That's been against the rules in the
>    DNS since forever.  Now you want to short-circuit the allocation
>    mechanism.  But we have an allocation mechanism for this.  In the
>    normal case, you apply to ICANN.  In an unusual case where the
>    protocol depends on this, then you can use this special-use
>    registry.  So you need to show that your protocol needs to depend
>    on this special-use label, and then we can register it under the
>    special use mechanism.  Otherwise go to ICANN.

+100.

I hope everyone here can agree on the above and we get back to discussing the actual draft.

v2.23.0 | Report a Bug | By Email