Re: [Ianaplan] [theresa.swinehart@icann.org: Re: [CWG-Stewardship] Fwd: [CCWG-ACCT] Ominous update on the IANA transition]

John Curran <jcurran@istaff.org> Sun, 03 May 2015 21:48 UTC

Return-Path: <jcurran@istaff.org>
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 43B511A8A42 for <ianaplan@ietfa.amsl.com>; Sun, 3 May 2015 14:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 TZWSpVxIrD58 for <ianaplan@ietfa.amsl.com>; Sun, 3 May 2015 14:48:48 -0700 (PDT)
Received: from relay.mailchannels.net (ar-005-i205.relay.mailchannels.net [162.253.144.87]) by ietfa.amsl.com (Postfix) with ESMTP id E477A1A8A3F for <ianaplan@ietf.org>; Sun, 3 May 2015 14:48:47 -0700 (PDT)
X-Sender-Id: duocircle|x-authuser|jcurran
Received: from smtp6.ore.mailhop.org (ip-10-204-4-183.us-west-2.compute.internal [10.204.4.183]) by relay.mailchannels.net (Postfix) with ESMTPA id A4BD960796; Sun, 3 May 2015 21:48:45 +0000 (UTC)
X-Sender-Id: duocircle|x-authuser|jcurran
Received: from smtp6.ore.mailhop.org (smtp6.ore.mailhop.org [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Sun, 03 May 2015 21:48:45 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: duocircle|x-authuser|jcurran
X-MailChannels-Auth-Id: duocircle
X-MC-Loop-Signature: 1430689725741:219680201
X-MC-Ingress-Time: 1430689725741
Received: from [64.88.227.134] (helo=[172.19.248.110]) by smtp6.ore.mailhop.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from <jcurran@istaff.org>) id 1Yp1kC-0007qQ-E5; Sun, 03 May 2015 21:48:46 +0000
X-Mail-Handler: DuoCircle Outbound SMTP
X-Originating-IP: 64.88.227.134
X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information)
X-MHO-User: U2FsdGVkX18pHijh09K7VUlOPFPvg0w0
Content-Type: multipart/alternative; boundary="Apple-Mail=_07508DF0-1240-401B-B65F-84D67E8E7E4A"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAOW+2dvEig9FDqKDtA26bwawbmgF+H+X_DJYbO5OjTy8nrpckw@mail.gmail.com>
Date: Sun, 03 May 2015 17:47:34 -0400
Message-Id: <92E5C2FA-25A9-46B2-9409-9D50DCB45942@istaff.org>
References: <20150501152117.GM68855@mx2.yitter.info> <CAOW+2dvEig9FDqKDtA26bwawbmgF+H+X_DJYbO5OjTy8nrpckw@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
X-Mailer: Apple Mail (2.2098)
X-AuthUser: jcurran
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/ZPViQlmS4j79vqCK-7hCdhAM2QU>
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] [theresa.swinehart@icann.org: Re: [CWG-Stewardship] Fwd: [CCWG-ACCT] Ominous update on the IANA transition]
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 21:48:50 -0000

On May 3, 2015, at 4:43 PM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> ...
> So in summary, even taking ICANN's legal concerns at face value, there were more transparent and open ways for those concerns to have been expressed and (potentially) clarified, ways that ICANN has shown itself quite capable of pursuing in other circumstances. 

Agreed - if a request for changes to the supplemental agreement were made publicly
of ICANN, then there is certainly a reasonable expectation of an equally public response.   

However, I’m not certain it is a fair expectation that in the midst of admittedly private 
discussions between IETF/IAOC and ICANN, ICANN should have unilaterally and 
publicly sent a letter of inquiry to NTIA (in fact, I can easily imagine circumstances 
where that act would be deemed rather anti-social...)

The entire community has known for more than a decade that ICANN has been
operating under two distinct agreements with respect to IANA registry operations, 
and the current and very active IANA stewardship transition planning efforts are 
all about finally straightening this mess out.   The IETF is quite reasonably trying 
to make progress via its proposed supplemental agreement changes, whereas 
ICANN has equally reasonable concerns that the planning for the IANA stewardship 
transition is still underway and we haven’t yet provided the required IANA stewardship
transition plan to NTIA, let alone received any indication back about proceeding to
implementation.

We’re going to have some interesting discussions in the coming months – discussions 
which are necessary in the process of coming to alignment on various IANA edge issues 
across the affected communities.   These will result in some entertaining reading from
time to time, but I suspect that everyone can keep a modicum of patience and faith nearby 
as necessary, with due consideration of long-term importance of the task before us to 
the global Internet community.

/John

Disclaimer:  my views alone; discard or use as desired.