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

"John R Levine" <johnl@taugh.com> Sun, 21 June 2015 13:44 UTC

Return-Path: <johnl@taugh.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 04E501A0404 for <ianaplan@ietfa.amsl.com>; Sun, 21 Jun 2015 06:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.563
X-Spam-Level: *
X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 q8fnVVPUZ8yX for <ianaplan@ietfa.amsl.com>; Sun, 21 Jun 2015 06:44:07 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C44A1A03FF for <ianaplan@ietf.org>; Sun, 21 Jun 2015 06:44:07 -0700 (PDT)
Received: (qmail 30286 invoked from network); 21 Jun 2015 13:44:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=764d.5586bfb1.k1506; bh=gEK3cUUu+sMGmVJFY+O5ESbI5YxPm+58Z5nhZSv4uk8=; b=fIGiCR2nc5odOZMvKz3d16mj2zyk0nxKsN9I0b9OtNv0ECtiBNc1sX9aPXKopjboh3LaXP0d5qzuQhMwuUjS5KGbs2DetZGWNbQWoAfCGUq9oLLBMvdI676JxTR09h7RZAJa7w2d3IbRXUxNaRsP9QHhofWxAF1FNFJZEgTucRhljoFlckaFnt00XdonQeftWpTy6LyORC83liN5VqqZMcQd6s4WLMntpZAoOuu/79P/Zd+Z3r9gpRd9jzdcrfUW
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=764d.5586bfb1.k1506; bh=gEK3cUUu+sMGmVJFY+O5ESbI5YxPm+58Z5nhZSv4uk8=; b=OcKxDz2JZZSHfhgBfgUfoXn6VhqoUEvdxu7z5Y6fcS+FQDevyr5NERtTuKMD8fdllGxazhc1bViflRsmUtprM3hlFd6Oi8TeShRUQZybtK/K4oeLL4y3vmoSljmV13L/XXr3RUzlCPrMgEGumiKqlIXyCp8IQpyrllOIqDXwbyQIzxtzSTAEIrNZTpUg/8pG8nEp2rx/Ki46Gacifs/xgZlSbWYIXxNIIab0snx2AwCrmKkjwyfCoGuQs6Lam7Uc
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 21 Jun 2015 13:44:17 -0000
Date: Sun, 21 Jun 2015 10:44:04 -0300
Message-ID: <alpine.OSX.2.11.1506211008240.48224@ary.local>
From: John R Levine <johnl@taugh.com>
To: dcrocker@bbiw.net
In-Reply-To: <55863ABF.8020903@dcrocker.net>
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>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/CPfaGEwcm3OoI60ne2Acr4egOT4>
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
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: Sun, 21 Jun 2015 13:44:09 -0000

> 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.  We've 
always considered their contents to be in the public domain; we need an 
agreement that confirms that.  It's always been available without 
restriction (no passwords or registration or the like) online. We need to 
confirm that, and it would probably be a good idea for IETF or ISOC to 
make daily snapshots of the protocol part of the current IANA web site.

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.

If ICANN-or-whoever were to start making trademark threats and didn't 
immediately back off when we said no, that would be clear evidence that 
they'd gone nuts and it's time for the exit strategy.  Leave the trademark 
with ICANN where it's more useful as a canary.

Finally, keep in mind the practical disadvantages to the IETF trust if it 
owns the trademarks.  It'll have to negotiate a license back to ICANN/PTI, 
and have the ongoing duty to decide if and when to defend them.  That puts 
yet more demands on the limited time of the IAOC.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.