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

Dave Crocker <dhc@dcrocker.net> Sat, 20 June 2015 20:54 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 8AF261AC39A for <ianaplan@ietfa.amsl.com>; Sat, 20 Jun 2015 13:54:18 -0700 (PDT)
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] 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 pDm5uKsHj_wv for <ianaplan@ietfa.amsl.com>; Sat, 20 Jun 2015 13:54:17 -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 0B9151AC399 for <ianaplan@ietf.org>; Sat, 20 Jun 2015 13:54:17 -0700 (PDT)
Received: from [172.28.2.94] ([131.90.57.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id t5KKs2au008127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 20 Jun 2015 13:54:05 -0700
Message-ID: <5585D2E3.9070801@dcrocker.net>
Date: Sat, 20 Jun 2015 13:53:55 -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: "ianaplan@ietf.org" <ianaplan@ietf.org>
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> <55855F68.4090906@gih.com> <CB2E8A54-4A4D-4DDF-BE62-B15BFC52C42D@istaff.org> <4F576AF8-A9D3-44BC-83EE-0CD86D5BF07D@gmail.com> <747E3649-D7C5-4AA2-9468-FF092961FEFD@istaff.org>
In-Reply-To: <747E3649-D7C5-4AA2-9468-FF092961FEFD@istaff.org>
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]); Sat, 20 Jun 2015 13:54:05 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/vU2czaR8sQM-UJU2ONSGgZujgJk>
Cc: Olivier MJ Crepin-Leblond <ocl@gih.com>
Subject: Re: [Ianaplan] [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: <http://www.ietf.org/mail-archive/web/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: Sat, 20 Jun 2015 20:54:18 -0000

On 6/20/2015 1:46 PM, John Curran wrote:
> On Jun 20, 2015, at 3:43 PM, Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>> There is one peculiar aspect of this, which is that currently the
>> IETF has no license to use the IANA trademark, yet it does appear
>> to use it with regularity.  If the IETF's field of use is covered
>> by the registration then there is an issue *today*, yet this topic

+1


> Bernard -
> 
> There’s quite a few peculiar aspects to all of this…  (e.g. the USG
> having a contract with ICANN to provide IANA protocol parameter
> registry services when the IETF has an MOU with ICANN for the same
> services;  the use of IANA mark in a very large context by IETF for
> years  before ICANN ever existed and yet the trademark now held by
> ICANN, etc.)

+1


...
> The exercise we now face is that the overall USG imprimatur (e.g. the
> IANA Functions contract) may be removed in the near future, and hence
> we need to make sure that we have arrangements that make sense going
> forward _in the absence of the USG saying ‘just make it all work’ via
> the IANA functions contract_

+10

Names matter, especially when they have long-established use.  A
trademark is a formalized aspect of naming.

The assumption that we can and should ignore matters of using the IANA
name and mark, when it is held by an organization that is a service
provider, rather than the originator or actual owner of the service,
seems an especially lax exercise in our responsibilities.

There is a real issue here.  It's easy to pretend we don't.  That would
be a mistake.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net