Re: [DNSOP] Top level names -- precision re categories and where are are the uncertainties?

Jaap Akkerhuis <jaap@NLnetLabs.nl> Tue, 07 July 2015 08:50 UTC

Return-Path: <jaap@NLnetLabs.nl>
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 6023C1A6FEB for <dnsop@ietfa.amsl.com>; Tue, 7 Jul 2015 01:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.884
X-Spam-Level:
X-Spam-Status: No, score=0.884 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CP27K5d14dVA for <dnsop@ietfa.amsl.com>; Tue, 7 Jul 2015 01:50:42 -0700 (PDT)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 641E61A6F0B for <dnsop@ietf.org>; Tue, 7 Jul 2015 01:50:42 -0700 (PDT)
Received: from bela.nlnetlabs.nl (localhost [127.0.0.1]) by bela.nlnetlabs.nl (8.14.9/8.14.9) with ESMTP id t678odmi054578; Tue, 7 Jul 2015 10:50:39 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
Message-Id: <201507070850.t678odmi054578@bela.nlnetlabs.nl>
To: Steve Crocker <steve@shinkuro.com>
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
In-reply-to: <EB26408C-8C6E-44E0-91FC-C2AF13D36D35@shinkuro.com>
References: <6CB05D82CE245B4083BBF3B97E2ED470C2759F@ait-pex01mbx01.win.dtu.dk> <6CB05D82CE245B4083BBF3B97E2ED470C275B2@ait-pex01mbx01.win.dtu.dk> <E225C721-7279-4053-97A2-2D63A155DA14@karoshi.com> <6CB05D82CE245B4083BBF3B97E2ED470C27602@ait-pex01mbx01.win.dtu.dk> <88E49F4B-64BD-4832-BD02-D1A882874E92@karoshi.com> <20150702234423.GB23022@mycre.ws> <EBDBDD70-046F-4E31-BDAC-A619EECD4F13@karoshi.com> <20150703012146.GA29948@mycre.ws> <DC13E07F-2203-4FE9-A67F-B5851A54298F@karoshi.com> <986E07DA-B174-4F81-BFB5-F5EAD46C506F@karoshi.com> <20150705003514.GD48722@mx2.yitter.info> <EB26408C-8C6E-44E0-91FC-C2AF13D36D35@shinkuro.com>
Comments: In-reply-to Steve Crocker <steve@shinkuro.com> message dated "Sat, 04 Jul 2015 18:26:43 -0700."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <54576.1436259039.1@bela.nlnetlabs.nl>
Date: Tue, 07 Jul 2015 10:50:39 +0200
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.4.3 (bela.nlnetlabs.nl [127.0.0.1]); Tue, 07 Jul 2015 10:50:40 +0200 (CEST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/c9h392xa2E5AJ2H7vY6wtJAyGAs>
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Top level names -- precision re categories and where are are the uncertainties?
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: Tue, 07 Jul 2015 08:50:44 -0000

 Steve Crocker writes:

 > Folks,
 > 
 > I`ve been watching the dialog on this list regarding to level names.
 > Attached is my attempt to clarify the state of affairs and identify the
 > loose ends.  Both PDF and pptx versions attached, the latter in case
 > someone is moved to edit the slides directly.


Either I don't understand the slides or they seem to be inconsistent.
As an example, you defines 8 "states" [1] and 8 definitions (later
called "Categories: when you give exanples. However the examples
doesn't match the definitions:

	Definition 2: Names that have not been formally recognized but
		are being used privately or for applications that have
		not yet become standard

	Definition 3: Two letter Latin characters that have not yet
		been assigned by the ISO 3166 maintenance agency but
		might be in the future.

	Category 2: xq

	Category 3: onion

Are these mistakes or purposely. (There seem to be more of these cases
on the slides).

	jaap



[1] I'm not sure whether this is a proper term. Can one state move to another?