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

John Curran <jcurran@istaff.org> Sun, 09 November 2014 07:45 UTC

Return-Path: <jcurran@istaff.org>
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 0BCA21A1A15 for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 23:45:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 kTCQEmXa3ywz for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 23:45:54 -0800 (PST)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B9C51A1A10 for <ianaplan@ietf.org>; Sat, 8 Nov 2014 23:45:54 -0800 (PST)
Received: from [64.129.1.11] (helo=[172.20.3.176]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1XnNC4-000Mdj-EO; Sun, 09 Nov 2014 07:45:52 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 64.129.1.11
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+4LlOOhEHsYHCJNtw0pCSJ
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <A7BD5ECF-11E4-42F1-A2B7-BF9B399635C3@gmail.com>
Date: Sat, 08 Nov 2014 21:45:48 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <14D42443-53E7-49FA-88DD-7F4BB6BC2DF4@istaff.org>
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.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/YTML2n0MfOSMRNW8MqaEhZ4B8I0
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, "Peterson, Jon" <jon.peterson@neustar.biz>, Andrew Sullivan <ajs@anvilwalrusden.com>, manning bill <bmanning@isi.edu>
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:45:56 -0000

On Nov 8, 2014, at 7:23 PM, 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.

It is not at all clear whether the IETF has any need to own the
IANA mark or domain; if the IETF determines that its use of the 
mark and domain are important to the protocol parameter function, 
then it only needs to ensure that it has the ability to use them -
that does not require ownership, only an appropriate agreement
providing for such use with the owner... (while there may be some
merit in being that owner, that is more than strictly necessary.)

/John

Disclaimer: my views alone.