[CWG-Stewardship] [IANA-issues] CWG RFP 2C - Draft Triage of IANA Functions Contract

Milton L Mueller mueller at syr.edu
Mon Oct 27 20:18:22 UTC 2014


Maarten

I guess you didn't understand my point. The possibility of separating the execution of the functions has nothing to do with how well or how poorly the IANA practical work is performed now. It has to do precisely with what you say needs attention: the oversight function. Oversight for names may or may not be optimized by combining it with oversight for the other functions. What happens, e.g., if one part is performed well and the other poorly? The requirements and procedures are radically different. This is a fact.

At any rate, I would encourage you to follow your own advice and "keep busy" developing a proposal that solve the problem for names, and let the other functions worry about their issues, and let the ICG worry about how they fit together when the proposals are in. Deal?

--MM


From: cwg-stewardship-bounces at icann.org [mailto:cwg-stewardship-bounces at icann.org] On Behalf Of Maarten Botterman GNKS
Sent: Monday, October 27, 2014 1:11 PM
To: cwg-stewardship at icann.org
Subject: Re: [CWG-Stewardship] [IANA-issues] CWG RFP 2C - Draft Triage of IANA Functions Contract

I'm with Avri on this. Never heard anyone being unhappy about the IANA practical work ("IANA functions") as such, I think the world sees that that works, and an old saying in IT is "don't fix it if it isn't broken". It works. Let's keep the focus on where it is to be, effectively: on the oversight function organization. A challenge big enough to keep us busy without also considering a different organization of the functions at the same time - in particular when there is no apparent need for that.

Or did I miss something?



From: cwg-stewardship-bounces at icann.org<mailto:cwg-stewardship-bounces at icann.org> [mailto:cwg-stewardship-bounces at icann.org] On Behalf Of Avri Doria
Sent: maandag 27 oktober 2014 3:20
To: cwg-stewardship at icann.org<mailto:cwg-stewardship at icann.org>
Subject: Re: [CWG-Stewardship] [IANA-issues] CWG RFP 2C - Draft Triage of IANA Functions Contract


On 27-Oct-14 00:31, Milton L Mueller wrote:

C.2.4. Assumes that all of the IANA functions are in the same entity. This assumption is not warranted at the present time.


Except that the assumption of this exercise is to change as few things as possible and an assumption that they can or even should be moved to seperate entities is not warranted.  The solition does not need to match the structure of the operational communities doing the recommendations.

Without an anaylisis of the effect of seperation, I think it unwise to assume they can or should be split.

I therefore would rather assume that the unity of IANA should be preserved until such time as it is proved that sperating them is the better solution.  And until it is proven that sperating them invovles no risk.  Even the IETF which is assuming it can pull out of IANA at any time has not done a complete analysis of the risks of doing so. Until we are sure that it does not pose a risk to the Internet, we ought to be careful about dumping this requirement.

avri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-stewardship/attachments/20141027/db63d679/attachment.html>


More information about the CWG-Stewardship mailing list