Re: [Ianaplan] it's more than that

John Curran <jcurran@arin.net> Sun, 03 May 2015 22:45 UTC

Return-Path: <jcurran@arin.net>
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 A2B141A8AA9 for <ianaplan@ietfa.amsl.com>; Sun, 3 May 2015 15:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, 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 q4_TcZu2dQKy for <ianaplan@ietfa.amsl.com>; Sun, 3 May 2015 15:45:25 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 5B5361A8AA8 for <ianaplan@ietf.org>; Sun, 3 May 2015 15:45:25 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id CCE81164E6B; Sun, 3 May 2015 18:45:24 -0400 (EDT)
Received: from chaedge01.corp.arin.net (chaedge01.corp.arin.net [192.149.252.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 53E3D164E3D; Sun, 3 May 2015 18:45:23 -0400 (EDT)
Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge01.corp.arin.net (192.149.252.118) with Microsoft SMTP Server (TLS) id 14.3.210.2; Sun, 3 May 2015 18:51:22 -0400
Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0224.002; Sun, 3 May 2015 18:45:16 -0400
From: John Curran <jcurran@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [Ianaplan] it's more than that
Thread-Index: AQHQhfLSz66wYBPTX02Hhe2cLmbFrg==
Date: Sun, 03 May 2015 22:45:15 +0000
Message-ID: <1EAA5791-76CA-4EEA-9546-CABBEE1D6524@arin.net>
References: <20150503214102.33356.qmail@ary.lan>
In-Reply-To: <20150503214102.33356.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.149.252.96]
Content-Type: multipart/alternative; boundary="_000_1EAA579176CA4EEA9546CABBEE1D6524arinnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/PtgrFzceo-m7cUxdvykCEmphPlI>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] it's more than that
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, 03 May 2015 22:45:27 -0000

On May 3, 2015, at 5:41 PM, John Levine <johnl@taugh.com<mailto:johnl@taugh.com>> wrote:
...
Personally, I'm more concerned about two things.  One is that the
CWG's plan boils down to ICANN overseeing itself through a wholly
owned subsidiary.  I realize there are supposed to be all sorts of
conditions indented to make this less absurd, but it seems absurd to
me.

John -

A very reasonable concern…  We’ve got a fairly difficult situation with respect to the names
community, in that ICANN is serving as their structure for organizing their community voice,
it’s their policy development structure, their oversight structure, and finally their IANA names
registry supplier.    (Wasn’t meant to be this way - DNSO community was to be a distinct
community-based organization from ICANN [much like RIRs/ASO],  develop their own policy,
and be sufficiently finically independent that it was actually ICANN that was to receive its
funding support from them…   instead, we’ve got a bit of vertical integration where it was
never originally intended.)

In any case, the act of extracting “the DNS community” from ICANN would be enormous,
so they went the other direction - move out the IANA and then work over ICANN’s structure
and accountability mechanisms so that they can have faith that ICANN truly represents the
DNS community.  There’s a just a few issues with that approach, but they’re working very
hard to make it happen.

More of an issue is the situation described in this article by the
generally perceptive Kieren McCarthy two days ago.  It reports that
ICANN has told the RIRs that ICANN won't even discuss any plan unless
it says that ICANN runs IANA forever:

http://www.theregister.co.uk/2015/05/01/icann_iana_latest/

If ICANN is really saying take it or leave it, I don't see that we
and the RIRs have any option but to leave it.  That would be a huge
hassle, but given ICANN's history, does anyone dare to give them
what is in effect a blank check?

I see zero chance of that happening - the plan components developed by both the IETF
community and numbers community (i.e. IANAplan and CRISP team proposals) contain
specific termination provisions, and I wouldn’t expect that either IETF or RIR leadership
would dare depart from those blueprints in such a fundamental way. To that end, I’ll note
that the RIR CEO’s just put out a statement regarding of the most recent meetings this
weekend, and it specifically notes -

      "In accordance with the NTIA’s expectations, and with the fundamental ethic of bottom-up,
       open and inclusive governance processes, it is important to reaffirm our common commitment
       to preserve the will of the community in the administration of number resources.”
<https://www.nro.net/news/nro-statement-on-the-internet-coordination-meeting-in-london-uk-may-2015>

FYI,
/John

John Curran
President and CEO
ARIN