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

Suzanne Woolf <suzworldwide@gmail.com> Tue, 04 February 2014 15:43 UTC

Return-Path: <suzworldwide@gmail.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 23D601A012A for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 07:43:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 CKhQTi8f031n for <dnsop@ietfa.amsl.com>; Tue, 4 Feb 2014 07:43:09 -0800 (PST)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 899041A011C for <dnsop@ietf.org>; Tue, 4 Feb 2014 07:43:09 -0800 (PST)
Received: by mail-ig0-f182.google.com with SMTP id uy17so8248050igb.3 for <dnsop@ietf.org>; Tue, 04 Feb 2014 07:43:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=e9k6LiRWhcoOWVIaI7707i7qot7q/qnACRXQUsS9+LU=; b=pxe4EeaD37lOrzx/UA1c/lJlwUfyieiqWq6a+McRUg5nTE88sZDXZJtyhVY3lHUVmk QgXPEqZRuaZDPt+8SD4sGnU2LT14ykyvMWBGBamhJeoH/7AOjZA/yABemr5BBlt9HxUm 2OVTanLmJ0ZvVomJuRmzdcmPw1KKUVV4bC7CwJpBrA/d15XnKH2x4hiYdwdWiRGJac3/ mlqyE51BGwTgo2Zuxpg7D8nK3kDF0gpWznEVvQM1KrH9WCeFoalbvA6TenRk5P60pLJo quxGvupFvPJlWaMViCTAo5RkFnl1z/jYyF5xGNAmw51150wAzhOg1sb1KEUaf+NAY5ba /UWA==
X-Received: by 10.43.137.5 with SMTP id im5mr1856227icc.55.1391528589150; Tue, 04 Feb 2014 07:43:09 -0800 (PST)
Received: from [172.19.131.154] ([12.130.127.94]) by mx.google.com with ESMTPSA id y9sm41011585igl.0.2014.02.04.07.43.05 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 07:43:08 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <20140204102956.GB16366@mx1.yitter.info>
Date: Tue, 4 Feb 2014 10:42:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E480A769-2241-4891-BFE8-7BA075E7D563@gmail.com>
References: <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> <CF160FB8.1983E7%jonne.soininen@renesasmobile.com> <20140204085134.GC17756@nic.fr> <20140204102956.GB16366@mx1.yitter.info>
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
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 15:43:11 -0000

Dear Colleagues,

On Feb 4, 2014, at 5:29 AM, Andrew Sullivan <ajs@anvilwalrusden.com>; wrote:
> I do not think we want to turn over the rock labelled, "Who owns the
> DNS name space?"  Under that rock live all manner of creatures from
> layer 9 and above.  We have two allocation procedures: regular
> allocation via IANA procedures (which happen to be defined right now
> in ICANN) and RFC 6761.  One of those procedures is the one we can
> exercise, and I still believe the only question is whether any
> particular registration attempt works under RFC 6761. 

In this spirit, I'd like to suggest that we assume for the sake of the current discussion that any apparent problem between ICANN and the IETF over the public DNS namespace can be resolved sensibly, so it's unnecessary to speculate on what ICANN knows, or what applicants for names under ICANN's process will or won't do, or whose process has precedence.

I think our job here has to be to discuss these drafts on their merits-- the operational impact of adding these names to the special use registry, or not, including guidance to implementors (if we converge on any) and precedents for other protocol and software developers in the future.

It also seems to me that if we come up with refinements or modifications to RFC 6761, we can write those up and share them with the community in the usual way.


best,
Suzanne