Re: [Ianaplan] update on trademarks and domains & IETF trust

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 17 February 2016 18:18 UTC

Return-Path: <ajs@anvilwalrusden.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 EF18D1B2AAE for <ianaplan@ietfa.amsl.com>; Wed, 17 Feb 2016 10:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001] 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 FJZUE-_YuEmy for <ianaplan@ietfa.amsl.com>; Wed, 17 Feb 2016 10:18:11 -0800 (PST)
Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id D77901B2A8A for <ianaplan@ietf.org>; Wed, 17 Feb 2016 10:18:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 56C97106CD for <ianaplan@ietf.org>; Wed, 17 Feb 2016 18:18:10 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFXFvGYBsWyI for <ianaplan@ietf.org>; Wed, 17 Feb 2016 18:18:09 +0000 (UTC)
Received: from mx2.yitter.info (unknown [IPv6:2601:18d:8600:87d9:d8be:fdfb:4bdf:3bc]) by mx2.yitter.info (Postfix) with ESMTPSA id 583081067C for <ianaplan@ietf.org>; Wed, 17 Feb 2016 18:18:09 +0000 (UTC)
Date: Wed, 17 Feb 2016 13:18:07 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20160217181807.GK66257@mx2.yitter.info>
References: <1ECCDCCB-234E-4201-9E20-F236D665766D@piuha.net> <950DAF9B-6F3B-4A8C-B270-78BFC25861FE@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <950DAF9B-6F3B-4A8C-B270-78BFC25861FE@piuha.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Wb8wk44xy6394JhLTX1e3XHpcZU>
Subject: Re: [Ianaplan] update on trademarks and domains & IETF trust
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, 17 Feb 2016 18:18:13 -0000

Dear colleagues,

On Tue, Jan 26, 2016 at 05:16:47PM +0200, Jari Arkko wrote:
> https://www.nro.net/pipermail/iana-ipr/

I will note that if you want to follow that list now as a subscriber,
you can.  You too can get our deathless discussion of IPR issues
delivered directly to your INBOX!  (It's still closed posting, however.)

We've also started work on a document of principles.  The draft is not
complete yet, and there are still some issues to work out, but I at
least would be extremely happy to hear remarks about what you see
there, if you have time to read and comment.  You can see the document
at
https://docs.google.com/document/d/1oR3nmHl1fK7BEWOBK65KyvnmhTJZX70j9q4Ne9i4ad4/edit?usp=sharing.
Unfortunately, it seems that in Google docs when you have read-only
access you can't see the comments either.

There are a couple issues that I think are quite important still to
sort out.

First, there's a set of things about the registration of iana.org.
The goal here is to use a registrar that can require multiple
approvals from different parties before changes are made.  That way
the IANA operator can have (and be assured of) technical control of
the domain while the registration is yet held by the Trust.  I know
there is at least one regisrtar that offers this sort of service
(Network Solutions, "Web Lock"), but if there are more I'd be happy to
hear about it so that we could point that out.

Second, there's the issue of the exclusive vs. non-exclusive license.
We have some registries that we treat as IANA registries but that are
strictly speaking not.  The enum registry, for instance, is not
operated by IANA.  Also, according to RFC 6557 the TZ Database is
operated by ICANN as if it were an IANA function under the IETF-ICANN
MoU but it is carefully called out as not an IANA function.  I'm not
sure whether this affects the license discussion (I'll be seeking
expert legal advice on this, but I wanted to note it as unsettled
business).

Third, and perhaps most important, is the discussion in 3.g.  There's
a tricky problem here.  The Trust will own the trademarks.  Under
trademark law, this means that the Trust will have a duty and a right
to enforce uses of the trademark.  So, if the Trust thinks that
there's a problem and it's gone unresolved, the Trust needs to be able
(in its sole discretion) to cancel the trademakk license to an IANA
operator.  At the same time, we want the individual operational
communities to have the power to select their operators.  The key
thing here in 3.g. is to see whether the balance is right given what
we want and the constraints of trademark law.

Obviously, any comments are welcome, but those are some substantive
issues that I think need attention.  Remember that this is not a
contract, but a set of principles under which we're going to work out
the final arrangements.  

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com