[CWG-RFP3] Option 5 - New IANA Entity

[Donna Austin]

Milton, you are correct, the NTIA announcement does not say “don’t have a separate IANA entity”, but it does say:

NTIA’s responsibility includes the procedural role of administering changes to the authoritative root zone file – the database containing the lists of names and addresses of all top-level domains – as well as serving as the historic steward of the DNS.  NTIA currently contracts with ICANN to carry out the Internet Assigned Numbers Authority (IANA) functions and has a Cooperative Agreement with Verisign under which it performs related root zone management functions.  Transitioning NTIA out of its role marks the final phase of the privatization of the DNS as outlined by the U.S. Government in 1997.

“The timing is right to start the transition process,” said Assistant Secretary of Commerce for Communications and Information Lawrence E. Strickling.  “We look forward to ICANN convening stakeholders across the global Internet community to craft an appropriate transition plan.”
From that I understand the task to be about developing a transition plan to replace the stewardship role that NTIA performs as well as their procedural role.

Stephanie Duchesneau characterized on the last call what I believe to be the crux of what we need to be considering:
•       The formation of an oversight body to replace the contractual oversight role that NTIA performed, responsible for holding IANA accountable to identified SLAs
•       The replacement of the ‘clerical’ role performed by NTIA
•       A method of recourse for registry operators who feel aggrieved by an IANA interpretation or implement of policy

(Apologies Stephanie if I have misrepresented your views).

Thanks,

Donna

[Description: Description: Description: ARI Logo]DONNA AUSTIN
Policy and Industry Affairs Manager

ARI REGISTRY SERVICES
Melbourne | Los Angeles
P  +1 310 890 9655
P  +61 3 9866 3710
E  donna.austin at ariservices.com<mailto:donna.austin at ariservices.com>
W  www.ariservices.com<http://www.ariservices.com/>

Follow us on Twitter<https://twitter.com/ARIservices>

The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.

From: Milton L Mueller [mailto:mueller at syr.edu]
Sent: Tuesday, 11 November 2014 8:41 AM
To: Donna Austin; 'James Gannon'; 'Greg Shatan'
Cc: 'RFP3'
Subject: RE: [CWG-RFP3] Option 5 - New IANA Entity

This is just wrong, Donna. The criteria the NTIA set are quite explicit and open and “don’t have a separate IANA entity” isn’t among them. More generally, as a principle, we should do that we think is best within the criteria, and not try to second-guess what the NTIA wants, or claim to be channeling the inner wishes of the NTIA. That makes for a distorted dialogue.

From: cwg-rfp3-bounces at icann.org<mailto:cwg-rfp3-bounces at icann.org> [mailto:cwg-rfp3-bounces at icann.org] On Behalf Of Donna Austin
I have some concerns that we’re potentially over-reaching here in terms of what we’ve been asked to do.

I don’t believe the NTIA is going to accept a proposal which calls for a separate IANA entity. In my mind, the NTIA announcement was evidence that they are happy with the current arrangement and how ICANN manages the IANA function – what they have asked the multi-stakeholder community to do is develop a mechanism that replaces the NTIA role in the process, not ICANN’s.

Thanks,

Donna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-rfp3/attachments/20141111/40896c86/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3765 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/cwg-rfp3/attachments/20141111/40896c86/image001-0001.png>