Re: [Ianaplan] CWG draft and its impact on the IETF

Milton L Mueller <mueller@syr.edu> Tue, 12 May 2015 06:43 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 D79351A1A52 for <ianaplan@ietfa.amsl.com>; Mon, 11 May 2015 23:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 nJ8I9bjohZHy for <ianaplan@ietfa.amsl.com>; Mon, 11 May 2015 23:43:23 -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 174A11A1A3D for <ianaplan@ietf.org>; Mon, 11 May 2015 23:43:23 -0700 (PDT)
Received: from EX13-MBX-06.ad.syr.edu (ex13-mbx-06.ad.syr.edu [128.230.108.137]) by smtp2.syr.edu (8.14.7/8.14.7) with ESMTP id t4C6hJc7032677 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 May 2015 02:43:20 -0400
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-06.ad.syr.edu (128.230.108.137) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 12 May 2015 02:43:01 -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.030; Tue, 12 May 2015 02:42:42 -0400
From: Milton L Mueller <mueller@syr.edu>
To: Bernard Aboba <bernard.aboba@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Ianaplan] CWG draft and its impact on the IETF
Thread-Index: AQHQjBpMEY3mz9BPA0WCyomEcYFu4J13fEsAgACeGQD//8j0UA==
Date: Tue, 12 May 2015 06:42:42 +0000
Message-ID: <1a38e8d374c54c22b1e19c8ed18ecf34@EX13-MBX-13.ad.syr.edu>
References: <5550F809.80200@cisco.com> <55511064.2000300@gmail.com> <CAOW+2dvBb4n4W=q7NoO_V1X+JoqvO1TWYBqPAEseY9T7vybj9Q@mail.gmail.com>
In-Reply-To: <CAOW+2dvBb4n4W=q7NoO_V1X+JoqvO1TWYBqPAEseY9T7vybj9Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [193.173.25.97]
Content-Type: multipart/alternative; boundary="_000_1a38e8d374c54c22b1e19c8ed18ecf34EX13MBX13adsyredu_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151, 1.0.33, 0.0.0000 definitions=2015-05-12_03:2015-05-09,2015-05-12,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1505120090
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/9UoGNAPA-rU29ZrjoWFIyujuYDQ>
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Eliot Lear <lear@cisco.com>
Subject: Re: [Ianaplan] CWG draft and its impact on the IETF
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: Tue, 12 May 2015 06:43:25 -0000


someone (ICANN or the communities or both) something, it needs to provide some definite benefit to compensate.  However, from what I can see, there is none.

MM: A very short-sighted comment. One would think that recent events would have brought home to everyone paying attention the risks of conceiving of the IANA functions as a monopoly of ICANN bundled in with (and dwarfed by) the naming policy development organization. I suggest a quick review of RFC 7500.

Just as a general admonition, IETFers who think that everything about ICANN will be the same once the NTIA and the USG leave the scene are living in a dream world. So your apparent comfort with the status quo needs to be re-examined in the light of future changes – changes that are NOT hypothetical

Typically wholly owned subsidiaries of a non-profit are created in situations where the subsidiary is expected to generate a profit, not a loss.

MM: This observation is completely irrelevant. This is a nonprofit environment and the primary considerations are accountability not profit or loss.

  Since the subsidiary is wholly owned by ICANN, the financial results can be consolidated, but consistently money-losing entities have a way of garnering extra scrutiny from taxing authorities (and from the executives and board members of the parent company).

MM: ICANN is tax-exempt, and if it has a problem along those lines recently, it is the fact that its naming policy activities generate too much money, not its losses. IANA functions currently account for about 3.6% of its overall budget. In terms of transparency, efficiency and the rationality and accountability of the overall system, it is a very good thing for budgets to be separated out and clearer.