Re: [DNSOP] [Ext] Re: Ed's comment s on Re: WGLC for draft-ietf-dnsop-sutld-ps

str4d <> Sun, 19 February 2017 20:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DB57C12953D for <>; Sun, 19 Feb 2017 12:14:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.451
X-Spam-Status: No, score=-0.451 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BRBL_LASTEXT=1.449, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ol3gyMbe4YDd for <>; Sun, 19 Feb 2017 12:14:23 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 20A6612950B for <>; Sun, 19 Feb 2017 12:14:22 -0800 (PST)
Received: from smtp.postman.i2p (unknown []) by postman.meeh.i2p (Postfix) with ESMTP id EDAD52E0F3A for <>; Sun, 19 Feb 2017 21:14:19 +0100 (CET)
X-Virus-Scanned: clamav-milter 0.97 on milter.postman.i2p
X-Mailer: smtp.postman.i2p - Official I2P Mailer
From: str4d <>
References: <> <> <> <20170216174816.088AFADF00@smtp.postman.i2p>
MIME-Version: 1.0
In-Reply-To: <20170216174816.088AFADF00@smtp.postman.i2p>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="NhicTrIGxtLkRiS8lsNqMnU4oSbH1FR55"
Message-Id: <20170219184747.2D6D6ADF17@smtp.postman.i2p>
Date: Sun, 19 Feb 2017 18:47:47 +0000
Archived-At: <>
Subject: Re: [DNSOP] [Ext] Re: Ed's comment s on Re: WGLC for draft-ietf-dnsop-sutld-ps
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 19 Feb 2017 20:14:25 -0000

On 02/17/2017 06:48 AM, Edward Lewis wrote:
> On 2/16/17, 12:23, "Suzanne Woolf" <> wrote:
> On Feb 16, 2017, at 11:46 AM, Russ Housley <> wrote:
> Ed: 
>>>> It would be good to provide a list of requests for new special use names.
>>>> Especially for a problem statement, this provides a way to estimate the 
>>>> "size and shape" of the problem and the urgency.
> (Russ:)
>>> No matter how you count, the volume will remain small if this is done 
>>> properly.  However, the special name requests can still be 
>>> important and urgent.
> (Suzanne:)
>> I also note it’s fairly difficult to estimate. 
>> ... .home/.corp/.mail ... .onion ... .alt ... .homenet 
> There is also a use of .id by Blockstack? as opposed to the ccTLD for Indonesia.  (This one just jumps to mind.)
> I did some looking and despite thinking there was once a backlog of a dozen, I haven't come across it in the mailing list.  (I could be wrong.)  What about .belkin, often cited as a string seen but not allocated?

You missed the ones that started all the drama ;P

- .gnu
- .zkey
- .exit
- .i2p
- .bit

> My goal is to see the problem statement document get more detailed so we can know when we've solved the problem.  ("The problem" is meant to be general, not necessarily the problem at hand.)
>> All of the drafts besides those for .onion, .alt, and .homenet have expired, which tells us nothing about whether or how they might come back.
> I don't think liveness of drafts is a sufficient measure of activity, considering the problem statement talks about uses from folks not engaging in the IETF process.  (If I'm hungry and in line at a restaurant, then walk away because the wait is too long, I'm still hungry.)

+1. I have a vested interest in the outcome of this discussion (being
involved in a relevant project), and offered to participate in the
problem statement design process. But with the significant general
headwind around the former, and never hearing back about the latter, I
decided my time was better spent on other things.

Also note that for at least some of these drafts, their inactivity and
expiry likely stems from the very loud "We are freezing the 6761 process
indefinitely" announcement. I doubt anyone outside of the existing IEFT
community would be willing to spend time working on a 6761-dependent
draft without knowing whether it will even exist in future.