Re: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval

Milton L Mueller <mueller@syr.edu> Sat, 20 June 2015 11:53 UTC

Return-Path: <mueller@syr.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 4B3CF1A1B67 for <ianaplan@ietfa.amsl.com>; Sat, 20 Jun 2015 04:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 V3mvM-jcwkfe for <ianaplan@ietfa.amsl.com>; Sat, 20 Jun 2015 04:53:51 -0700 (PDT)
Received: from smtp2.syr.edu (smtp2.syr.edu [128.230.18.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93B571A1B3E for <ianaplan@ietf.org>; Sat, 20 Jun 2015 04:53:51 -0700 (PDT)
Received: from EX13-MBX-11.ad.syr.edu (ex13-mbx-11.ad.syr.edu [128.230.108.142]) by smtp2.syr.edu (8.14.7/8.14.7) with ESMTP id t5KBrjsn013892 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 20 Jun 2015 07:53:46 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-11.ad.syr.edu (128.230.108.142) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sat, 20 Jun 2015 07:53:33 -0400
Received: from EX13-MBX-13.ad.syr.edu ([128.230.108.144]) by EX13-MBX-13.ad.syr.edu ([128.230.108.144]) with mapi id 15.00.0847.040; Sat, 20 Jun 2015 07:53:15 -0400
From: Milton L Mueller <mueller@syr.edu>
To: "avri@acm.org" <avri@acm.org>, "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval
Thread-Index: AQHQp32LsZylGtbpo0KLECmw5T4dNJ2ufyIAgAXFPACAAEyXgIAAVXYAgABlEcA=
Date: Sat, 20 Jun 2015 11:53:15 +0000
Message-ID: <9d673c1e7cc14f68aea47bdbbe887bbb@EX13-MBX-13.ad.syr.edu>
References: <D1A45F80.1B274%grace.abuhamad@icann.org> <90E3156B-428B-4A61-92B7-BAC932842FB5@viagenie.ca> <557F63E2.40302@gmail.com> <20150619155355.GI17513@mx2.yitter.info> <55847B53.60106@gmail.com> <5584C304.9000806@acm.org>
In-Reply-To: <5584C304.9000806@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [201.234.152.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2015-06-20_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1502090000 definitions=main-1506200206
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Jn0fnVd7Rpc99ExULxQ7uVnAI5o>
Subject: Re: [Ianaplan] Fwd: For your Information: CWG-Stewardship Response for Chartering Organization Consideration and Approval
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: Sat, 20 Jun 2015 11:53:53 -0000


> -----Original Message-----
> I admit that despite the respect I have for the IETF and its Trust, given that
> the Trust's fiduciary responsibilities are solely to the IETF, I argue that the
> IANA domain names and any trademarks associated with them should be
> transferred to the PTI along with the other assets necessary for doing its job.
> And if that can't happen, then remaining with ICANN seems the next best
> option to me.

This doesn't work if you want a community to be able to change its IANA functions operator. If one particular IANA functions operator holds the mark then it has a kind of lock-in that the principle of separability should not permit them to have. And asking a particular IANA functions operator to make the marks and domain "perpetually and freely available" to actual or potential competitors sets up an obvious conflict of interest that is likely to cause trouble. Besides, telling ICANN or PTI that the license cannot be exclusive means in effect that ICANN or PTI don't actually own it, so it's not clear why you would want it to be there. The IETF, on the other hand, has no such conflict of interest and does have a real and impartial interest in ensuring that the name associated with the basic registries created by its own standards are used in an appropriate way. 

I can't take seriously people who say "if we ever have to change IFO everything will be so messed up that it won't matter who controls the marks;" this is neither logically true (one can posit many scenarios in which it isn't) and it is obvious that fighting or confusion over the marks would make even that bad scenario worse. 

Again it seems like you are needlessly re-litigating the issue here. IANAPLAN and CRISP have a proposal for how to handle the marks and domain that are compatible. CWG doesn't. Let CWG propose how it wants to reconcile the incompatibility. Then you can discuss its merits.