Re: [Ianaplan] "IANA.ZONE" and other entities and strategies

John C Klensin <john-ietf@jck.com> Wed, 24 June 2015 18:17 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D268C1ACE1F for <ianaplan@ietfa.amsl.com>; Wed, 24 Jun 2015 11:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level:
X-Spam-Status: No, score=-0.711 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rAT2H1gQJQoK for <ianaplan@ietfa.amsl.com>; Wed, 24 Jun 2015 11:17:07 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3751ACE1D for <ianaplan@ietf.org>; Wed, 24 Jun 2015 11:17:05 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Z7pEJ-000Exx-4m; Wed, 24 Jun 2015 14:16:59 -0400
Date: Wed, 24 Jun 2015 14:16:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jefsey <jefsey@jefsey.com>
Message-ID: <9653AAA5D37A7957DBE268F1@JcK-HP8200.jck.com>
In-Reply-To: <20150624135328.C89CE1A9163@ietfa.amsl.com>
References: <20150619170708.84611.qmail@ary.lan> <3F18936E1587B5F2BB89E800@JcK-HP8200.jck.com> <55847BE9.9040507@gmail.com> <5584BC64.7060403@gmail.com> <alpine.OSX.2.11.1506192151170.47260@ary.local> <5584D664.90003@gmail.com> <alpine.OSX.2.11.1506201928040.47864@ary.local> <55863ABF.8020903@dcrocker.net> <alpine.OSX.2.11.1506211008240.48224@ary.local> <5586EB11.5030404@dcrocker.net> <alpine.OSX.2.11.1506211400250.48860@ary.local> <5587A015.9030700@cisco.com> <alpine.OSX.2.11.1506221032250.50421@ary.local> <55881331.9070902@dcrocker.net> <alpine.OSX.2.11.1506221056420.50578@ary.local> <5588FE8B.3040806@gmail.com> <55896464.2040803@cisco.com> <20150623155648.DDE9F1A6F11@ietfa.amsl.com> <0D43D8143E5C5F21538340A0@JcK-HP8200.jck.com> <5589D32C.2040809@gmail.com> <20150624135328.C89CE1A9163@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/EJl-AbMQ2693W4z1c5KDBIeUKrs>
Cc: ianaplan@ietf.org
Subject: Re: [Ianaplan] "IANA.ZONE" and other entities and strategies
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jun 2015 18:17:09 -0000


--On Wednesday, June 24, 2015 15:53 +0200 Jefsey
<jefsey@jefsey.com> wrote:

> Sorry, not the time to comment now, but thank you to be so
> damnly "NSAn". At least this is loud and clear.

Jefsey,

You may find it loud and clear, but, from my perspective, it
sounds like name-calling using a term I assume your are
intending to be pejorative but that may not mean the same thing
to all of us.   I don't think name-calling is ever helpful to a
discussion, nor, especially in this case, do I think it
contributes any clarity.

You may or may not like (or agree with) our reasoning or where
it leads us, but I, and I believe both Brian's response to my
note, and Russ's quite separate explanation of IETF procedures
vis-a-vis blocking publication of documents, were intended to be
calm, constructive, and adult responses to your note.  As
someone who often ends up defending you and your efforts to
contribute to the Internet, it saddens me that you could not (or
decided not to) respond in a similar fashion and tone.

      best regards,
         john