Re: [Internetgovtech] Transition to the web

Miles Fidelman <mfidelman@meetinghouse.net> Sun, 13 July 2014 11:49 UTC

Return-Path: <mfidelman@meetinghouse.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 5BF241B2B45 for <internetgovtech@ietfa.amsl.com>; Sun, 13 Jul 2014 04:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.88
X-Spam-Level:
X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 JuUE-cpaXkPk for <internetgovtech@ietfa.amsl.com>; Sun, 13 Jul 2014 04:49:30 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 101261B2A8F for <internetgovtech@iab.org>; Sun, 13 Jul 2014 04:49:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 195B5CC080 for <internetgovtech@iab.org>; Sun, 13 Jul 2014 07:49:24 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1LYRxd58E0w2 for <internetgovtech@iab.org>; Sun, 13 Jul 2014 07:49:15 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 4CACCCC07E for <internetgovtech@iab.org>; Sun, 13 Jul 2014 07:49:15 -0400 (EDT)
Message-ID: <53C2723A.7030101@meetinghouse.net>
Date: Sun, 13 Jul 2014 07:49:14 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1
MIME-Version: 1.0
CC: internetgovtech@iab.org
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>
In-Reply-To: <7D8B6314-F38B-4B49-A146-5AE59F371C14@virtualized.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/CthXNYtJurkQHRgUzNxG7jPGmE0
Subject: Re: [Internetgovtech] 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 11:49:31 -0000

David Conrad wrote:
>
>>> What would stop the IETF/IESG/IAB from deciding to pick their own "IANA" and having that IANA provide protocol parameter allocation, modifications, and deletion services under the terms the IETF/IESG/IAB permits?
>> Well, that is the $64,000 dollar question underlying all this transition stuff, isn't it.
> 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.

Isn't that what I just said?

>> 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.
>

Umm.. yes, it is.  ICANN plays its role in the process, because the DOC 
contract says that it must perform those functions.  And it 
cross-subsidizes those functions from its income stream from other IANA 
functions.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra