Re: [Ianaplan] Fwd: [CWG-Stewardship] ICG request concerning IANA trademark and iana.org domain name

Dave Crocker <dhc@dcrocker.net> Sun, 21 June 2015 16:49 UTC

Return-Path: <dhc@dcrocker.net>
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 CCC5A1B29CE for <ianaplan@ietfa.amsl.com>; Sun, 21 Jun 2015 09:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.4
X-Spam-Level: *
X-Spam-Status: No, score=1.4 tagged_above=-999 required=5 tests=[BAYES_99=3.5, BAYES_999=0.2, RCVD_IN_DNSWL_MED=-2.3] autolearn=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 dZ7vwua4vEWX for <ianaplan@ietfa.amsl.com>; Sun, 21 Jun 2015 09:49:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78B081B29C9 for <ianaplan@ietf.org>; Sun, 21 Jun 2015 09:49:31 -0700 (PDT)
Received: from [172.28.66.170] (host186189.pge.com [131.89.186.189]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t5LGnRqE021523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 21 Jun 2015 09:49:30 -0700
Message-ID: <5586EB11.5030404@dcrocker.net>
Date: Sun, 21 Jun 2015 09:49:21 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: John R Levine <johnl@taugh.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>
In-Reply-To: <alpine.OSX.2.11.1506211008240.48224@ary.local>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 21 Jun 2015 09:49:31 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/fpHNEVkt2d2aMgB92LUhy9ET7d8>
Cc: ianaplan@ietf.org
Subject: Re: [Ianaplan] Fwd: [CWG-Stewardship] ICG request concerning IANA trademark and iana.org domain name
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 21 Jun 2015 16:49:32 -0000

On 6/21/2015 6:44 AM, John R Levine wrote:
>> John, the premise of legal agreements that deal with exit processes is
>> that the concerns of interest are for circumstances that are not
>> pleasant and cooperative.
> 
> Of course.  The important things about the parameter registries are what
> they contain and how they're available, not what they're called. 

Yeah, that's been a common refrain from various folk.  What's amusing
about it is that we are a community that worries quite about about the
use of names and addresses for getting access to resources.  Yet here,
we are being told they don't matter.

The idea that it won't make much difference if we have to change from a
well-established and heavily used name and address, for getting at the
resources under discussion, seems a tad counter-intuitive...


> If things go kerflooie, we'll find someone else to run the protocol
> registry.  They will need the data from the current registry and the
> processes which are documented (pretty well) in RFCs.  But they don't
> need to call it IANA or to call the web site iana.org.

This seems to take the view that instantaneous obsolescence of the
rather massive infrastructure of documents using that name and address
won't have any interesting operational effects.  That view also doesn't
match typical experience.



d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net