Re: [DNSOP] Some distinctions and a request - Have some class?

Suzanne Woolf <suzworldwide@gmail.com> Sat, 04 July 2015 16:28 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 A86B01ACE31 for <dnsop@ietfa.amsl.com>; Sat, 4 Jul 2015 09:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, 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 AysrC96DiKQY for <dnsop@ietfa.amsl.com>; Sat, 4 Jul 2015 09:28:19 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77F621AC3A0 for <dnsop@ietf.org>; Sat, 4 Jul 2015 09:28:19 -0700 (PDT)
Received: by qkbp125 with SMTP id p125so90789368qkb.2 for <dnsop@ietf.org>; Sat, 04 Jul 2015 09:28:18 -0700 (PDT)
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:cc :content-transfer-encoding:message-id:references:to; bh=j8iZgvmynTA6LoHfWm5z33fqw8i9ZqFODd5khflYehc=; b=t5QPg5SkhYpnKtjsr5CmVaGmOWV889xLrG4tu2FI5R3MBY8k//jh6c+MEWLsDxX7vs baB+B4qYOTEKc8itwCRMj88zuVGSUlZJyhMIrt1HwzmkxGsuIpLv2a4bo0KSw4xQEkaQ XJlkRGG6DSJeMbhY5DgeN140La9kD1NpiEalJsFjQJav1KR0R3bExFyvqOTSfLeBuiEj a1J2aYeNkinFR44qghQFttO4ovspjKCFE6x0Wu2q4cQbYdUxA781gyWuAo+LLTKhRO33 0NAG7zlmqKapGj6z/jebRQdkEtyt6/ae4scHqrTfwkPoGyTFFq7XFyvmx3aG4eJDT9vb 7o0A==
X-Received: by 10.140.133.18 with SMTP id 18mr63177746qhf.84.1436027298762; Sat, 04 Jul 2015 09:28:18 -0700 (PDT)
Received: from ?IPv6:2601:181:c002:25ee:39f7:2ea4:58fe:b18b? ([2601:181:c002:25ee:39f7:2ea4:58fe:b18b]) by mx.google.com with ESMTPSA id f199sm1307693qka.9.2015.07.04.09.28.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Jul 2015 09:28:17 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2074.6\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <017CF015-8A06-40D5-9ECF-B7B7E208C7AF@frobbit.se>
Date: Sat, 04 Jul 2015 12:29:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <27B81BB7-B254-40CD-B245-F74C4F395229@gmail.com>
References: <20150704063120.2380.qmail@ary.lan> <017CF015-8A06-40D5-9ECF-B7B7E208C7AF@frobbit.se>
To: Patrik Fältström <paf@frobbit.se>
X-Mailer: Apple Mail (2.2074.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/qJGSsPMjrwoZl3UgN0puycSyIwg>
Cc: bmanning@karoshi.com, dnsop@ietf.org, John Levine <johnl@taugh.com>
Subject: Re: [DNSOP] Some distinctions and a request - Have some class?
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: <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 Jul 2015 16:28:20 -0000

(no hats)

> On Jul 4, 2015, at 3:12 AM, Patrik Fältström <paf@frobbit.se> wrote:
> 
> Once again:
> 
> ICANN do say what strings in the name space should be TLDs.
> 
> IETF do say what strings in the name space should NOT be TLDs.

In the interests of precision in our discussion: I’m not convinced that’s actually the case, and I’m not convinced it’s consistent with what we’ve said in the conversation so far. I *think* it loses exactly the distinction that we started the thread with.

It seems to me, from long experience of both organizations, that ICANN says what names should and shouldn’t be in the DNS root zone— a specific instantiation of the namespace, tied to use in a specific database (the public DNS) and the DNS protocol. (Enormous chunks of the Applicant Guidebook, and of the deliberations in the new gTLD program, were devoted to discussion of what names should *not* be in the root zone.)

It further seems to me that the IETF says what names it considers to be in the namespace for other reasons, such as enabling deployment of new protocols (as already pointed out upthread, it’s perhaps unfortunate but undoubtedly true that people are doing this and we may want to enable it).

Avoiding collisions between DNS and non-DNS use of domain names is probably important to us (to some degree that’s what we’re trying to decide). But I have thought, and continue to think, that we make a serious mistake if we regard it as our purpose to “say what strings in the name space should NOT be TLDs.”  The IETF delegated that responsibility long ago to someone else, and for good reason.

> The rest are just strings waiting to end up in one of the two groups.

I’m not sure I agree with this either, but will have to think further.


best,
Suzanne