Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Miles Fidelman <mfidelman@meetinghouse.net> Wed, 05 November 2014 12:47 UTC

Return-Path: <mfidelman@meetinghouse.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 93E9E1A1ADF for <ianaplan@ietfa.amsl.com>; Wed, 5 Nov 2014 04:47:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 mJbAhnjrYcwE for <ianaplan@ietfa.amsl.com>; Wed, 5 Nov 2014 04:47:04 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8701A1A5F for <ianaplan@ietf.org>; Wed, 5 Nov 2014 04:47:04 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 82630CC050 for <ianaplan@ietf.org>; Wed, 5 Nov 2014 07:47:03 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gOySQZ92OJ22 for <ianaplan@ietf.org>; Wed, 5 Nov 2014 07:46:54 -0500 (EST)
Received: from new-host-3.home (pool-96-237-159-213.bstnma.fios.verizon.net [96.237.159.213]) by server1.neighborhoods.net (Postfix) with ESMTPSA id BE73DCC04B for <ianaplan@ietf.org>; Wed, 5 Nov 2014 07:46:53 -0500 (EST)
Message-ID: <545A1C3D.6040209@meetinghouse.net>
Date: Wed, 05 Nov 2014 07:46:53 -0500
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30
MIME-Version: 1.0
CC: ianaplan@ietf.org
References: <GLEAIDJPBJDOLEICCGMNMENECNAA.rhill@hill-a.ch> <316AD206-26EC-43F7-8669-A5B3CA6B3F52@virtualized.org> <54594160.90009@meetinghouse.net> <19EC0395-987B-4036-BAA7-5BC75B000EAC@virtualized.org>
In-Reply-To: <19EC0395-987B-4036-BAA7-5BC75B000EAC@virtualized.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/-QHFsa3joQK1ZQAscG57SHD_t2E
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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: Wed, 05 Nov 2014 12:47:05 -0000

David Conrad wrote:
> Miles,
>
> On Nov 4, 2014, at 11:13 AM, Miles Fidelman <mfidelman@meetinghouse.net> wrote:
>> Well, it might be helpful to know that history.  At one point, SRI was IANA,
> No. SRI was "The NIC". The IANA was the IANA (before that "the numbers czar"). These are different entities. In many cases, the IANA would often direct The NIC to do stuff.

My mistake.  Memory clouds with time.  Jon was at ISI.
> I believe it more accurate to say that the IANA function was performed at the behest of the IETF community and that the folks who performed that function were funded indirectly by the USG. That is, my understanding is that the IANA was _NOT_ a line item in any budget, rather the support costs that paid for Jon's, Joyce's, et al. salary were pulled from the "Tera-node" Project among others.
>
>> and still is, who actually has legitimate claim to the trademark, and how does that play against the domain registration policy?
> It would seem the US PTO believe that ICANN has the claim to the trademark. I'll admit not knowing the intricacies of how trademarks impact domain registration policy.

Which kind of leads to the question of how ICANN ended up with the 
trademark.

As to domain registration policy: ICANN administers (sets?) the UDRP 
(Uniform Domain Name Dispute Resolution Policy) as part of its 
agreements with registrars, which includes this:

*a. Applicable Disputes.* You are required to submit to a mandatory 
administrative proceeding in the event that a third party (a 
"complainant") asserts to the applicable Provider, in compliance with 
the Rules of Procedure, that

(i) your domain name is identical or confusingly similar to a trademark 
or service mark in which the complainant has rights; and

Miles


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra