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

Bob Hinden <bob.hinden@gmail.com> Mon, 22 June 2015 17:02 UTC

Return-Path: <bob.hinden@gmail.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 5610E1B3072 for <ianaplan@ietfa.amsl.com>; Mon, 22 Jun 2015 10:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 AKA6x-VlR06U for <ianaplan@ietfa.amsl.com>; Mon, 22 Jun 2015 10:02:03 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A44B31B3070 for <ianaplan@ietf.org>; Mon, 22 Jun 2015 10:02:03 -0700 (PDT)
Received: by iecvh10 with SMTP id vh10so23082870iec.3 for <ianaplan@ietf.org>; Mon, 22 Jun 2015 10:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=oMCsuW7VxPBhKh8leG9nG7Vv0z1DEqIjGW80RIORz0c=; b=R7QTyDw0ZfQ/y+3GgYJk2LyRbAe3DP07fwMMyW4Xxrp91iTxKUUueYuTv6S7eA+Nuf oQcDCKWmBpe1XNinsWjlDrjfNtimpx8hgPPJW6z61vqk7PSwEq9OtsSjb0vNZfjYNZxN x0Tpw13BhN+uecocoZATeIruAhDotglRGi8RPEYyTn4hiYIEcn2agCH6v11lhnaDja2T auW0ObS04OmV9XiWsdDzIKQEfjCrxpegXQXiweLcVjzClqdiwBfQMbmUlwKZY8MACG3q 3Wt0tolXvyVR1fG4j/pJO9urx+ZrH4731pIIxuNeUzp5XQeLuzcI8zjhVjSuBAdhL0sH lBZQ==
X-Received: by 10.107.15.153 with SMTP id 25mr39479798iop.44.1434992523102; Mon, 22 Jun 2015 10:02:03 -0700 (PDT)
Received: from [10.0.0.38] (c-71-202-19-53.hsd1.ca.comcast.net. [71.202.19.53]) by mx.google.com with ESMTPSA id i85sm13141798iod.41.2015.06.22.10.02.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jun 2015 10:02:01 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_971E30CC-AE08-47D3-9302-232986A7E35F"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <20150622153724.GE21352@mx2.yitter.info>
Date: Mon, 22 Jun 2015 10:01:56 -0700
Message-Id: <ED093345-9655-47A7-9BE5-516313DB9219@gmail.com>
References: <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> <5585D205.1000603@gmail.com> <20150621222321.GA20470@mx2.yitter.info> <940887304e1a476fa183f6a39313ede7@EX13-MBX-13.ad.syr.edu> <20150622153724.GE21352@mx2.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/NLdUPHA0STXIqN1MOpcrc7bwjoQ>
Cc: ianaplan@ietf.org, Bob Hinden <bob.hinden@gmail.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
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 17:02:06 -0000

Andrew,

> Well, either that, or the ability of one side to pour resources into a
> dispute even if their legal foundation is poor.  One of the facts we
> have to face is that one of the parties that would be in such a
> dispute has way more lawyers and money than we do.  I do see certain
> force in the position that, given the IETF's situation, it would be
> really good for the IETF if the IETF Trust had control of the mark and
> domain name.  But that brings us to another argument, made I think
> best by Avri: why is giving up that control to the IETF (or an
> organization whose fiduciary responsibility is just to the IETF) at
> all in the interests of the other communities?

I was thinking of responding to Avri, and will do it here.

The summary of the IETF Trust (from http://trustee.ietf.org) includes:

    The purposes of the trust include the advancement of educational and public
    interest by acquiring, holding, maintaining and licensing certain existing and
    future intellectual property and other property used in connection with the Internet
    standards process and its administration, for the advancement of the science and
    technology associated with the Internet and related technology.

I think this clearly includes the activities of the three communities (names, addresses, and protocols) if the IETF Trust was to hold the IANA domain and trademark IPR.  The work of the names and addressing communities fit within this scope.  They are all working to advance the science and technology associated with the Internet and related technology.

Further, the IETF clearly does more than act in it’s own self interest.  It is open to everyone, it does it work by volunteers, and it publishes it’s work freely without charge.  It does not have a revenue stream based on it’s work.  It only purpose it to create a lot of the technology that makes the Internet work.

I think the IETF Trust would be a fine place to hold the IANA related IPR if the community desired it.

Bob (former IETF Trust trustee)



> 
> If it's not, then we revert to the position that we need a common and
> neutral trust to hold this, and at that point it seems to me we're
> back to re-inventing ICANN.
> 
>> Nowhere in this process is there a stipulation that says you are bargaining with ICANN, or NTIA, or ICG or the names community, or anyone else, and have to "give something up" to be able to achieve a gain.
> 
> Of course not.  But if different communities want dramatically
> different things, then there are only two possibilities:
> 
> 1.  Nobody gets what they want.
> 
> 2.  Somebody gets what they want.  In this case, either someone just
> loses, or else the loser is persuaded to give up.  The "persuasion"
> usually under such circumstnaces involved some other gain.  That's
> what bargaining is always like.
> 
>> So if all 3 communities can come to consensus on the movement of the IANA-related IPR into the IETF Trust, then it will happen.
> 
> Well, yes, but that's the counterfactual right now: we know that one
> of the communities has a proposal that is incompatible with one of the
> other communties.  So we're in the stage where people are having a
> tussle over that movement of the IPR.
> 
>> I can think of all kinds of things that can happen in the names community, in the CCWG, in Congress, in NTIA, among goverments, but nothing happening here poses a serious risk.
>> 
> 
> I'm pretty sure this isn't what you mean, but what I read in your text
> is that if the IETF said, "Whoa, we can't agree to that," it wouldn't
> present a risk to the transition.  Suppose, for instance, that we're
> not able to get the affirmations that the registries are in the public
> domain and that the incumbent IANA operator would co-operate in a
> transtion.  Suppose, worse, that the outcome was in fact an explicit
> IPR claim over the content of the registries (a not completely
> imaginary possibility -- someone suggested it to me at one point).
> You're not saying that the IETF's position in such a case wouldn't
> derail the transition, right?  You just mean that, given the position
> the IETF formed consensus around, that's not likely to be the thing
> that causes trouble, correct?
> 
> Best regards,
> 
> A
> 
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
> 
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan