Re: [Ianaplan] who or what is the proper authority to control the IANA domain and the trademark?

Marc Blanchet <marc.blanchet@viagenie.ca> Sun, 09 November 2014 22:17 UTC

Return-Path: <marc.blanchet@viagenie.ca>
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 A4C261A874E for <ianaplan@ietfa.amsl.com>; Sun, 9 Nov 2014 14:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level:
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594, 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 O04qNVlAohA8 for <ianaplan@ietfa.amsl.com>; Sun, 9 Nov 2014 14:17:10 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC481A8741 for <ianaplan@ietf.org>; Sun, 9 Nov 2014 14:17:10 -0800 (PST)
Received: from h226.viagenie.ca (h226.viagenie.ca [206.123.31.226]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 3810740398; Sun, 9 Nov 2014 17:17:07 -0500 (EST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <D0851062.138E6C%jon.peterson@neustar.biz>
Date: Sun, 09 Nov 2014 12:17:03 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <971ECAD7-935D-4CD2-ACCF-2CB6F1F19BE9@viagenie.ca>
References: <8c4a23d4c0aa4679a47c24b07c71d1a4@EX13-MBX-13.ad.syr.edu> <545E624F.10501@meetinghouse.net> <D0851062.138E6C%jon.peterson@neustar.biz>
To: Jon Peterson <jon.peterson@neustar.biz>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/5zc5KHqSdUm8U_NAJcSVFOl3zDU
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: [Ianaplan] who or what is the proper authority to control the IANA domain and the trademark?
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, 09 Nov 2014 22:17:12 -0000

> Le 2014-11-09 à 11:11, Peterson, Jon <jon.peterson@neustar.biz> a écrit :
> 
>> Milton L Mueller wrote:
> </snip>
>>> I do not see how any reasonable person can maintain that the fate of
>>> the IANA domain and mark are not relevant to the IANA transition. Any
>>> adequate IANA transition plan has to deal with both those issue.
> 
> The fate (future ownership, etc) of the IANA domain and mark are essential
> to the IANA transition. They just aren't essential to the question of how
> the IETF uses the IANA. The IETF ICG response is about how the IETF uses
> IANA and what the IETF needs from IANA going forward. Other stakeholders
> will be providing other perspectives. The ICG should combine and consider
> these as appropriate.
> 
>>> My position is simple: the IANA domain and mark should be associated
>>> with whatever entity is running the IANA functions. And if ICANN¹s
>>> performance of those functions is contingent upon IETF approval, as it
>>> should be, those resources have to be movable. I have not heard a
>>> single argument against this. I have only heard: ³we don¹t want to
>>> deal with this.
> 
> Speaking as someone with no skin in that game, it sounds reasonable that
> the IANA domain and mark should be associated with whatever entity is
> running the IANA function, sure. In fact it sounds platitudinous. I don't
> however think that ICANN's performance of the IANA function overall is
> contingent on the IETF's approval, and it probably shouldn't be. Only the
> operation of the protocol parameter registries is covered by our agreement
> with ICANN for IANA (RFC2860). The other aspects of IANA's performance
> probably shouldn't be monitored or evaluated by the IETF, as we don't
> operationally interact with them.
> 
> Should the protocol parameter registry be movable? Of course it should.
> And we have the power to move that resource any time we want, irrespective
> of the portability of domain names and trademarks. I don't want our
> flexibility to be limited by getting us all tangled up in obligations
> about trademarks.
> 
>>> As I understand your position, it is that ICANN should be the entity
>>> that holds them perpetually. You have not said this directly, but the
>>> argument ³the fate of the marks and the domain doesn¹t matter² is, de
>>> facto, an argument that ICANN is the proper entity to hold them in
>>> perpetuity because that is who holds them now. Please explain to us
>>> why ICANN should be given a permanent property right in those
>>> resources when it does not and should not have a permanent,
>>> inalienable right to run the IANA functions.
> 
> I doubt it would be possible, or appropriate, to gauge IETF consensus on
> the question of whether or not a corporation should own a perpetual right
> to a trademark. The scope of the IETF and its expertise are more narrow
> than you seem to think. No one here is likely to defend the proposition
> that ICANN or any other entity should have a permanent property right. But
> we are not the right organization to take a stand on this kind of
> question. Surely other organization participating the ICG process are in a
> better position to provide this feedback than us.

I agree with what Jon wrote. My only additional comment is that we should really « raise » the overall issue within our response to ICG.

Marc, as individual.

> 
> Jon Peterson
> Neustar, Inc.
> 
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan