IETF Logo Mail Archive

Re: [DNSOP] On .ZZ

Jared Mauch <jared@puck.nether.net> Thu, 21 November 2019 07:21 UTC

Return-Path: <jared@puck.nether.net>
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 EFBE91209BA for <dnsop@ietfa.amsl.com>; Wed, 20 Nov 2019 23:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 v23rDEASi2nI for <dnsop@ietfa.amsl.com>; Wed, 20 Nov 2019 23:21:32 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF65A120048 for <dnsop@ietf.org>; Wed, 20 Nov 2019 23:21:32 -0800 (PST)
Received: from dhcp-9354.meeting.ietf.org (dhcp-9354.meeting.ietf.org [31.133.147.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id C2A5E5400DC; Thu, 21 Nov 2019 02:21:29 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAHXf=0pOVM_MHypgL7uV88242ciBUXGpx6waUetxBbZhvth1gA@mail.gmail.com>
Date: Thu, 21 Nov 2019 02:21:25 -0500
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD7D7E78-1760-429A-858A-4560BD066D47@puck.nether.net>
References: <CAHXf=0pOVM_MHypgL7uV88242ciBUXGpx6waUetxBbZhvth1gA@mail.gmail.com>
To: Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Z0r-veQt-FJ2EGmY85Jqez1k_SQ>
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:21:37 -0000

.ZZ makes as much sense as anything else to be honest, virtually anything is going to conflict with some acronym or name out there.

- Jared

> On Nov 21, 2019, at 2:18 AM, Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com> wrote:
> 
> Setting the basic issue aside (I'm still a bit torn) I agree with
> Warren that it would need a string that has a meaning.
> 
> ..ZZ would remind me of long beards and loud motorcycles for the rest
> of my life.. https://de.wikipedia.org/wiki/ZZ_Top
> 
> best,
> Alex
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email