[Internetgovtech] Costs (Was: Re: Transition to the web)

Jari Arkko <jari.arkko@piuha.net> Sun, 13 July 2014 12:07 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: internetgovtech@ietfa.amsl.com
Delivered-To: internetgovtech@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5491B2B63 for <internetgovtech@ietfa.amsl.com>; Sun, 13 Jul 2014 05:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level:
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] 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 9SvWGb9pxNCD for <internetgovtech@ietfa.amsl.com>; Sun, 13 Jul 2014 05:07:05 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id EDF1B1B2B62 for <internetgovtech@iab.org>; Sun, 13 Jul 2014 05:07:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1D8B42CCC0; Sun, 13 Jul 2014 15:07:04 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wegofMroL8w; Sun, 13 Jul 2014 15:06:55 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 14FBA2CC48; Sun, 13 Jul 2014 15:06:55 +0300 (EEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_4ED3DEB5-1D62-4305-9F6B-4324F02DE8A2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7D8B6314-F38B-4B49-A146-5AE59F371C14@virtualized.org>
Date: Sun, 13 Jul 2014 15:06:45 +0300
Message-Id: <E38A5683-897B-44E2-AFA2-510383602389@piuha.net>
References: <6.2.5.6.2.20140708142055.0d5fbb78@elandnews.com> <D1AC4482BED7C04DAC43491E9A9DBEC3998608C6@BK-EXCHMBX01.blacknight.local> <20140709161653.GM59034@mx1.yitter.info> <9B506E73B33873103AE5EC52@JcK-HP8200.jck.com> <20140709171401.GB2935@mx1.yitter.info> <53BD843F.1070304@cs.tcd.ie> <53BD84BB.7000002@meetinghouse.net> <53BDA867.7090701@gmail.com> <53BE602F.7020108@firsthand.net> <53BE6384.5030504@cs.tcd.ie> <53BE69D2.9070509@firsthand.net> <6.2.5.6.2.20140711000259.0cc016e8@resistor.net> <53BFD828.3070007@firsthand.net> <53C06E7C.4010903@gmail.com> <CAD_dc6ihUvV8SDkmoc3fGHWoOoR6nFhRz-=tgCjKnuNvRO2JXw@mail.gmail.com> <53C0F1D9.3090400@cisco.com> <53C17B5C.4090600@abenaki.wabanaki.net> <C5750A628D4D973F3C44F6DC@JcK-HP8200.jck.com> <53C1B2C6.40501@meetinghouse.net> <72F8472D-2913-4BEC-9260-6DAC7791BBF8@virtualized.org> <53C1E977.4050306@meetinghouse.net> <7D8B6314-F38B-4B49-A146-5AE59F371C14@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/WuGdr7CpuIEEOmSjO6RGYOCd3zY
Cc: internetgovtech@iab.org
Subject: [Internetgovtech] Costs (Was: Re: Transition to the web)
X-BeenThere: internetgovtech@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <internetgovtech.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/internetgovtech/>
List-Post: <mailto:internetgovtech@iab.org>
List-Help: <mailto:internetgovtech-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2014 12:07:07 -0000

> No. The transition stuff is trying to figure out how to not disrupt the way the Internet works while removing NTIA from the functions it provides. As far as I can tell, those functions are:
> 
> 1) ensure ICANN has followed its own processes in validating changes to the root zone;
> 2) provide a mechanism by which ICANN can be held accountable for its actions;
> 3) facilitate obtaining exemptions for dealing with entities under sanction in order to provide registry services; and
> 4) reduce the risk ICANN will be subject to inappropriate legal, economic, and/or geo-political pressure.
> 
> (I've been told #3 isn't that big an issue anymore, but don't have direct knowledge -- haven't been at ICANN for 4 years now and I'm told things have changed)
> 
> However, instead of dealing with that issue, my impression is that people on this list and elsewhere have been far more focused on whether or not a mailing list is used for communication instead of a web-based forum and how that demonstrates ICANN is incompetent, inappropriate, and/or evil.

The above list is indeed good.

>> The question of who pays for the IETF-related IANA functions seems to be one of those details.
> 
> 
> That is not a function that is currently performed by NTIA. Section 4.4 and 4.5 of RFC 2860 is explicit that ICANN may not charge for IETF-related IANA services. The existing arrangement appears to be working and I have heard no one (other than perhaps yourself) arguing that this is an issue that needs to be addressed as part of the transition. In particular, neither the chair of the IETF, the chair of the IAB, nor ICANN's CEO have suggested that the MOU needs to be revised/terminated to allow ICANN to charge for IETF-related registry services. I'm unclear why you think it is an issue.

For what it is worth, David is right above. I would like to suggest that focusing on the costs is the wrong way to approach the issue. Lets first ensure that we have a system that performs the right functions, and I think we are already close to that. From the 10.000 ft perspective the costs are not such a big issue that they should drive the transition in any particular direction. At least not for protocol parameters.

Jari