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

manning bill <bmanning@isi.edu> Sun, 09 November 2014 07:07 UTC

Return-Path: <bmanning@isi.edu>
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 26A5D1A19F2 for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 23:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.194
X-Spam-Level:
X-Spam-Status: No, score=-4.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594] 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 867mfvTgfbNA for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 23:07:13 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44CB51A19EF for <ianaplan@ietf.org>; Sat, 8 Nov 2014 23:07:13 -0800 (PST)
Received: from dhcp-8972.meeting.ietf.org (dhcp-8972.meeting.ietf.org [31.133.137.114]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id sA976XeL018152 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 8 Nov 2014 23:06:44 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="windows-1252"
From: manning bill <bmanning@isi.edu>
In-Reply-To: <A7BD5ECF-11E4-42F1-A2B7-BF9B399635C3@gmail.com>
Date: Sat, 08 Nov 2014 23:06:32 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B256811C-CEF5-49F4-955D-B486DB1EF122@isi.edu>
References: <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <545ABCB0.5080206@meetinghouse.net> <8f3dcda6c3db4cd8be1b77444f987d59@EX13-MBX-13.ad.syr.edu> <D0805C27.136BE7%jon.peterson@neustar.biz> <059f2b06a7b44f09b7568d8966861fb8@EX13-MBX-13.ad.syr.edu> <D0824FAD.137A42%jon.peterson@neustar.biz> <E314302D-5179-4899-9DB7-A3AF18C134E8@gmail.com> <20141108155153.GB37292@mx1.yitter.info> <D083864D.138D18%jon.peterson@neustar.biz> <A6D94EF5-BD92-4080-8C18-E415BD0BB880@isi.edu> <C78A1523-316F-46A1-9FCE-D0D205679C84@gmail.com> <13B26DE5-315D-453F-B89B-377CCD338ED9@isi.edu> <A7BD5ECF-11E4-42F1-A2B7-BF9B399635C3@gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/ZQ0QLT5Hs6fcD3ZLgP_3phdjiwA
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>, "Peterson, Jon" <jon.peterson@neustar.biz>
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: Sun, 09 Nov 2014 07:07:19 -0000

exactly.  protecting the NAME/BRAND.    I would have thought this effort would have focused on the use of multiple, cooperating parties to 
perform a specific suite of functions, and not have fallen into the rathole of branding and trademark.  

“The entities responsible for the list of tasks identified in NTIA contract# (and follow-ons),  therein referred to as “The IANA””
"The listed tasks are;  a) severable, and b) may be performed by entities not referred to by any of the exiting marks:  (IANA, ICANN, NTIA, RIR, ARIN.RIPE,LACNIC,APNIC,AFRINIC, NRO, ASO, 
GNSO, ccNSO, GAC, IETF, ISOC, IAB, (fill in the rest of the blanks).”
“If the tasks are severed, there will need to be agreed on criteria to ensure the parties are performing their functions for the global benefit of the users of the Internet and not to the benefit of the tasked parties.”
“In the event of non-compliance, there will need to be agreed on criteria for re-assignment of the affected task(s) to qualified parties”


Or are those statements fundamentally wrong?

If these types of questions are deemed inappropriate or untimely - I am sorry.  

/bill
PO Box 12317
Marina del Rey, CA 90295
310.322.8102

On 8November2014Saturday, at 21:23, Bernard Aboba <bernard.aboba@gmail.com> wrote:

> The owner of trademark can use it to assert ownership not only of a directly corresponding domain name, but also of similar names. 
> 
> However that does not necessarily imply that it is desirable for the IETF Trust to own the IANA trademark. Trademarks (particularly ones involving registrations in multiple countries) can be quite expensive to register and protect. So unless the Trust has examined the costs involved and finds them manageable, it might make more sense to focus on the conditions for transfer to a successor contractor.
> 
>> On Nov 8, 2014, at 6:27 PM, manning bill <bmanning@isi.edu> wrote:
>> 
>> so you are more worried about the name and not the function?
>> 
>> /bill
>> PO Box 12317
>> Marina del Rey, CA 90295
>> 310.322.8102
>> 
>>> On 8November2014Saturday, at 17:05, Bernard Aboba <bernard.aboba@gmail.com> wrote:
>>> 
>>> 
>>>> On Nov 8, 2014, at 2:36 PM, manning bill <bmanning@isi.edu> wrote:
>>>> 
>>>> Removal of or rehoming some of the trappings of power (who controls IANA.*) seems like a niche question at best.
>>> 
>>> [BA] I would agree that our goal should be to ensure that this is a non-issue.
>>> 
>>> However, I do NOT agree that the issue can be ignored. Trademarks in particular can be very powerful things, and it is quite common for trademark owners to challenge uses that even vaguely resemble the trademark, even in uses that might appear peripheral. 
>>> 
>>> The responsible thing here is to avoid amateur lawyering and get advice from counsel.
>>