[Ianaplan] returning to the topic of IANA trademarks and domains

Jari Arkko <jari.arkko@piuha.net> Fri, 18 September 2015 23:03 UTC

Return-Path: <jari.arkko@piuha.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 8B29F1B3902 for <ianaplan@ietfa.amsl.com>; Fri, 18 Sep 2015 16:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 g1E26Flm9BGB for <ianaplan@ietfa.amsl.com>; Fri, 18 Sep 2015 16:03:52 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 532CE1B3900 for <ianaplan@ietf.org>; Fri, 18 Sep 2015 16:03:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9805D2CC6B for <ianaplan@ietf.org>; Sat, 19 Sep 2015 02:03:50 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZYytAsWqYLj for <ianaplan@ietf.org>; Sat, 19 Sep 2015 02:03:49 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D3E642CC5C for <ianaplan@ietf.org>; Sat, 19 Sep 2015 02:03:48 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
From: Jari Arkko <jari.arkko@piuha.net>
X-Pgp-Agent: GPGMail 2.5.1
Content-Type: multipart/signed; boundary="Apple-Mail=_4318BAD2-517C-4020-A339-EFE173E221AC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Date: Fri, 18 Sep 2015 16:03:45 -0700
Message-Id: <695427AA-50BB-4C51-9764-4DCEAFF31993@piuha.net>
To: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/gbPZgVdXAKIQKJRM1po6Nbod-6w>
Subject: [Ianaplan] returning to the topic of IANA trademarks and domains
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: Fri, 18 Sep 2015 23:03:55 -0000

We have discussed trademarks and domains in the past, and came
to a basic agreement. Meanwhile, the names community has also
indicated that the “IPR in an independent entity” model is acceptable
to them. But the details for any of this are left for implementation phase.
That phase will take place once the overall transition plan goes forward.

The IETF Trust has worked in the background to understand the
situation better, and obviously, if something needs to be done,
ultimately there has to be agreements and concrete actions need
to be taken. But before we are that far, we have to talk about the
overall approach and find a common ground about the implementation
with all three communities.

With this in mind, the Trust has written up a high-level
description of what it believes the approach could be.
We thought that this would be useful for both this WG
as well as for communication with others.

Please see the description below. The Trust would
appreciate any feedback you have. The goal is that
after getting that feedback (and after revision as needed)
we could have a description that can be used in discussing
further implementation steps.

Jari

---

As a part of their transition proposal, the Internet Number
Community stated that it was their preference that the IANA
trademark and iana.org domain would be transferred to an entity
independent of the IANA Numbering Services Operator, and from their
perspective the IETF Trust would be an acceptable candidate for this
role.

On 8 February, the ICG asked the IETF and Internet Number Community
to coordinate their transition proposals with regards to the
trademarks and domains. Discussion in the IETF working group
indicated that the proposals can be compatible.

At the request of the IANAPLAN WG the IETF Chair on 17 February 2015
asked the IETF Trust whether the Trust would be willing to hold IANA
intellectual property.  Citing Article 5.2 of the Trust Agreement
whereby the Trust could hold rights in intellectual property and
domain names relevant to the IETF, the Trustees on 19 February said
they would be willing to hold the IANA intellectual property.  See
http://trustee.ietf.org/documents/Trust-Minutes-2015-06-25-01.pdf

At the request of the IETF Chair the IETF Trust has engaged in
discussions with the Internet Number Community about the possibility
of the Trust assuming this responsibility.  The following is some
background of the Trust’s position and an overview of how the role
and responsibilities may be fulfilled.

While this fulfillment is a part of implementation rather than the
ICG proposal currently out for public comment, the IETF Trust wants
to ensure progress on determining those implementation steps. The
Trust is of course only one of the possible ways to satisfy the
requirements from the Internet Number Community. Nevertheless, the
Trust wanted to start by suggesting an overall framework for one way
of satisfying the requirements. There will be a time to discuss the
details, but first it would be good to have an understanding if this
overall framework is something that works for the relevant
communities. This is only an early proposal. Feedback  and
suggestions are very welcome.

The Trust believes it would need to enter into three different types
of agreements to effect the transfer of the IANA intellectual
property (IP) and to enter into licensing arrangements with the IANA
service provider(s).

These agreements include:

1.  An Agreement between ICANN and the IETF Trust transferring the
IANA IP to the IETF Trust

2.  Community Assurance Agreements between the IETF Trust and each
of the names, numbers, and protocol communities (the IANA communities)
regarding the Trust’s commitments to each as further described below, and

3.  Agreement(s) whereby the IETF Trust provides for the use of the
iana.org domain, or a subdomain, and licenses the use of the IANA
trademarks to the IANA service provider(s) selected by the IANA
communities.

The Trustees are open, in principle, to the idea of entering into
these agreements. The Trust understands that each community
would need to follow its own internal processes before entering
into any agreements, or selecting an IANA service provider.

The Community Assurance Agreements with the IANA communities
would establish and recognize the responsibilities for each community
to identify and enter into agreement with their selected service provider,
and for the IETF Trust to provide, update, and revoke licenses as needed to
support these selections.

In order to preserve the value and integrity of the IANA trademarks,
the IETF Trust would maintain, license and monitor the use of the
trademarks.  Trust actions would include enforcement against
unauthorized users and monitoring the quality and uses by the
licensed user(s). The Trust would work with the relevant IANA
communities to address issues involving a licensee before taking
action to maintain the quality of the trademarks.

The exact details of the agreements would be subject to negotiation
among the affected parties.