Re: [dns-dir] Draft requesting reservation of special-use domain names

Patrik Fältström <paf@frobbit.se> Thu, 28 November 2013 10:45 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: dns-dir@ietfa.amsl.com
Delivered-To: dns-dir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 465721ADFDB for <dns-dir@ietfa.amsl.com>; Thu, 28 Nov 2013 02:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.651
X-Spam-Level:
X-Spam-Status: No, score=-0.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_22=0.6, LOTS_OF_MONEY=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=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 AU768QFWQaPr for <dns-dir@ietfa.amsl.com>; Thu, 28 Nov 2013 02:45:44 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id A677D1AD939 for <dns-dir@ietf.org>; Thu, 28 Nov 2013 02:45:43 -0800 (PST)
Received: from junior.frobbit.se (unknown [192.165.72.12]) by mail.frobbit.se (Postfix) with ESMTPA id D61EE2272F; Thu, 28 Nov 2013 11:45:41 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_4537CB64-9F54-4ECC-B174-74B58F6B16EF"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Patrik Fältström <paf@frobbit.se>
In-Reply-To: <3387707A-201E-490C-9B65-3EB6B35DA8E1@NLnetLabs.nl>
Date: Thu, 28 Nov 2013 11:45:39 +0100
Message-Id: <7DCFF968-AEF2-4BF0-83AC-FAA7B2630D71@frobbit.se>
References: <5286231D.4030104@innovationslab.net> <52863898.5080100@innovationslab.net> <8F0B436C-85D2-4566-A80B-40710DF9D476@ogud.com> <B6B47E1A-678D-4856-BE54-E34ADC7E98F8@townsley.net> <73C44405-6048-4031-9FA5-BCDFA70160A4@frobbit.se> <84D57F70-CCA3-4412-989E-0FAB089ECEEF@gmail.com> <31C42EE0-8D1F-4D7C-8E8C-43ACE5F61B04@frobbit.se> <528D2782.4070208@sonic.net> <B42C50EA-39CE-415E-9CBA-0F0471CAC519@NLnetLabs.nl> <F7DEECA9-5E88-4888-986B-D63DC66FA8B9@gmail.com> <3387707A-201E-490C-9B65-3EB6B35DA8E1@NLnetLabs.nl>
To: Kolkman Olaf <olaf@nlnetlabs.nl>
X-Mailer: Apple Mail (2.1822)
Cc: IETF DNS Directorate <dns-dir@ietf.org>, Erik Nordmark <nordmark@sonic.net>
Subject: Re: [dns-dir] Draft requesting reservation of special-use domain names
X-BeenThere: dns-dir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNS directorate discussion list <dns-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dns-dir/>
List-Post: <mailto:dns-dir@ietf.org>
List-Help: <mailto:dns-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-dir>, <mailto:dns-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 10:45:45 -0000

On 28 nov 2013, at 10:46, Olaf Kolkman <olaf@nlnetlabs.nl> wrote:

> On 28 nov. 2013, at 01:57, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> 
>> Is there some reason to think those names might be delegated from the root?  My understanding is that the review process for name delegation would identify such names as "not to be delegated" if there is significant use now, otherwise, they are safe to delegate. 
> 
> At this moment .corp and .home are ‘on-hold’ (indefinitely?).
> 
> There is also an SSAC recommendation to have some of these strings permanently reserved, and SSAC is looking towards the IETF (correct Patrik?)

A few details here:

1. SSAC do not say exactly what strings are "high risk". .HOME and .CORP can be viewed as "easy", but what about ".MAIL" etc?

2. SSAC do say that "not delegate" is not enough, we do believe some strings should explicitly be for "private use". Which matches quite well what 6762 says.

3. SSAC could have directly pointed at the Appendix G, if it was clear that that was normative, and so could ICANN. But what I heard from at least one person cc:ed is that that is _not_ normative.

Question: Can IESG/IAB make a decision on the appendix "due to widespread use, misunderstanding and unclear situations etc etc we do believe those strings should not be allocated as TLDs"?

Can IESG/IAB even say yes/no to such a question without an appeal?

Is an I-D and RFC needed that clarifies status of Appendix G?

I.e. I think some IETF action is needed. Having ICANN do "too much" instead of referring to IETF -- specifically if we go down the path of "defining some strings to be TLDs for private use" -- would be dangerous.

I think personally IETF is the body that should say not only what subset of IP address space RIRs can allocate things out of but also what subset of the available bitstring space ICANN can use. Which IETF has done with "hostname" definition (cough, cough,...) and IDN2008.

So, $10.000 question: What is the path forward for "allocation of some strings for private use"?

Do IETF need a formal question from ICANN? Would that really help?

   Patrik