IETF Logo Mail Archive

Re: [DNSOP] On .ZZ

Paul Wouters <paul@nohats.ca> Thu, 21 November 2019 07:27 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8397312004C for <dnsop@ietfa.amsl.com>; Wed, 20 Nov 2019 23:27:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 scnBLvuwlDwT for <dnsop@ietfa.amsl.com>; Wed, 20 Nov 2019 23:27:01 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 B79D6120048 for <dnsop@ietf.org>; Wed, 20 Nov 2019 23:27:01 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 47JWN32rRZz5Br; Thu, 21 Nov 2019 08:26:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1574321219; bh=T+lP7BhNyAKav8VjaJo9Tmnbi3XlcGithWUiNVvrng0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=GIqJ1k010MWXwUV87K6qgeeGUb5JnGKnm6H2dXSC3LzhvoKZtlvERyBuPT5YjWl18 pJiqEcAJEoYbh/QfqVROQenNqz0BLzCgW4bO7Sep+ZSHyRIyqoQ7+Ws27Q1XyOp5jc NYT5y5HEp2DKV0A+d7AZeCfwWFgis6wFfGk0ULbE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id NYrtKLJMBQqR; Thu, 21 Nov 2019 08:26:57 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 21 Nov 2019 08:26:57 +0100 (CET)
Received: from [31.133.136.79] (dhcp-884f.meeting.ietf.org [31.133.136.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id B4557607CC4B; Thu, 21 Nov 2019 02:26:56 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <CAHXf=0pOVM_MHypgL7uV88242ciBUXGpx6waUetxBbZhvth1gA@mail.gmail.com>
Date: Thu, 21 Nov 2019 15:26:44 +0800
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <35F0456A-2BA5-4021-AA9D-A86889E74AE6@nohats.ca>
References: <CAHXf=0pOVM_MHypgL7uV88242ciBUXGpx6waUetxBbZhvth1gA@mail.gmail.com>
To: Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9Hq4MscaSrsegfDJ3QnyTHnCHdA>
Subject: Re: [DNSOP] On .ZZ
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Nov 2019 07:27:03 -0000


> On Nov 21, 2019, at 15:18, Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com> wrote:
> 
> 
> ..ZZ would remind me of long beards and loud motorcycles for the rest
> of my life.. https://de.wikipedia.org/wiki/ZZ_Top

English speaking people can’t even agree on how to pronounce this name......

Having an undelegated .zz is also not guaranteed to be free of security issues, for example if ICANN delegates .zzz there will be interesting typo attacks possible in this weird private space.

Finally, I agree. People want something semantic and more pronounceable.

Paul

v2.23.0 | Report a Bug | By Email