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

John C Klensin <john-ietf@jck.com> Mon, 22 June 2015 14:43 UTC

Return-Path: <john-ietf@jck.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 AAE5A1A1A19 for <ianaplan@ietfa.amsl.com>; Mon, 22 Jun 2015 07:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.09
X-Spam-Level:
X-Spam-Status: No, score=0.09 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, 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 FY3Y81eJhZ1x for <ianaplan@ietfa.amsl.com>; Mon, 22 Jun 2015 07:43:39 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C0E21ACD9D for <ianaplan@ietf.org>; Mon, 22 Jun 2015 07:43:32 -0700 (PDT)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Z72wa-0004DQ-Hg; Mon, 22 Jun 2015 10:43:28 -0400
Date: Mon, 22 Jun 2015 10:43:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: John R Levine <johnl@taugh.com>, Eliot Lear <lear@cisco.com>
Message-ID: <57D51369E208BE3EF27AD0B5@JcK-HP8200.jck.com>
In-Reply-To: <alpine.OSX.2.11.1506221032250.50421@ary.local>
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> <5586EB11.5030404@dcrocker.net> <alpine.OSX.2.11.1506211400250.48860@ary.local> <5587A015.9030700@cisco.com> <alpine.OSX.2.11.1506221032250.50421@ary.local>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Xzl7nVIn5AFszen429sPbQ4VNqk>
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: <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: Mon, 22 Jun 2015 14:43:40 -0000


--On Monday, June 22, 2015 10:36 -0300 John R Levine
<johnl@taugh.com> wrote:

>> If we were to put the legal questions aside, I imagine we
>> would all argue that of course the IETF should be able to
>> continue to use the name IANA no matter who the IFO was.
>> Would you agree with that statement?
> 
> Of course.  But it makes no sense to put the legal questions
> aside.  If the future IANA continues to be reasonable, which
> we all hope and expect it will, things will work fine and it
> doesn't matter who holds the trademark and domain.  If things
> get nasty, it stil doesn't matter, we're schrod no matter who
> holds the trademark and domain.

I don't know that I would go quite that far or be quite that
bleak in my predictions, but it seems to me that, if things
turned nasty:

(i) Even if we (aka the IETF Trust) held the names, if things
got nasty there could be challenges about who could use them and
for what.  The advantage I see in using the IETF Trust (or any
other neutral party with similar interests and history) is that
the IETF Trust's charter (and consistent practices) would make
the intent that the name and domain were to be used for the
benefit of the whole Internet community (and agreement to that
intent) clear (see below).

(ii) If things do get nasty enough that the use of the names
were seriously challenged, we would, as several of us have
pointed out, need to move / rename the registries as a stability
matter; we could not wait until those issues, whatever they
were, were resolved.

(iii) As Andrew pointed out, once we start moving things, it is
extremely unlikely that there would be any going back.  In
retrospect, we probably should have established
iana-protocols.org, iana-addresses.org, etc. --or at least
established clear subdomains for the three sets of registries
and used them in our terminology-- in 2002 or earlier.  Too late
now.

Even if the intent were clearly established (by an IETF Trust
agreement or otherwise [1], it does not prevent "nasty" should a
really bad situation develop.  It doesn't even prevent someone
in the names community from wondering whether, if we pulled the
protocol registries out and were suddenly stuck with the costs,
we (or IAOC or the IETF Trust) wouldn't suddenly see the names
as a revenue opportunity.  I'm confident we wouldn't do that,
both of you are probably confident we wouldn't do that, but, for
someone who is not personally familiar and involved with
whatever passes as an IETF culture, it is as reasonable a
question as our worrying about exclusive licenses and where the
trademark and domain name live seems to be to us.

best,
   john


[1] To save someone else suggesting it, one could also establish
that intent through some amount of lawyer-speak in a
hypothetical PTI charter or bylaws.   Maybe it could even be
done in a way that would be consistent with languages about
exclusive licenses.  But, given that bylaws and charters can be
changed, even that would come back to my comments about trust
several days ago.