[discuss] P1 version 2 - I will update from time to time - this one is important

Dr. Ben Fuller ben at fuller.na
Sun Jan 19 20:52:37 UTC 2014


I would start with some analysis of point 2. What are the kinds of changes that ICANN/IANA recommend? Can we develop a typology? The aim being to divide changes into those that are mainly operational/technical and those that would be viewed as problematic. I assume that operational/technical changes can go through in a straightforward manner. We analyse the problematic changes and then focus on what kinds of structures/procedures would be needed to deal with them in a way that is acceptable the widest number of parties. ICANN has 16 years of data.

Three points. One I have a sense that many, and I include myself, don't have a grasp of what takes place when root zone changes are made. What are the procedures? What are the checks and balances? Understanding the process as well as the kind of changes that are made will help to keep the discussion focused. 

Two, I assume that there have been controversial/problematic changes to the root zone. Have there been? How were they dealt with? There is the possibility that some are complaining just because it is the US that has the final approval. Still, it will be useful to get those who complain to put forward their concerns as clearly as possible so they can be addressed. 

Three, the US House and Senate have both overwhelmingly voted resolutions that direct the US Government to maintain control over the root. Given the current climate in Washington, we cannot expect much of a change here, hence solutions also have to be acceptable inside the Beltway. Peter Dengate Thrush spoke of this a few days ago from a different angle.


On Jan 19, 2014, at 9:59 PM, George Sadowsky <george.sadowsky at gmail.com> wrote:

> Change of title to focus solely on root zone functions:
> P1 (ver.2). US Government involvement in IANA root zone functions.
> 1. The Internet Assigned Names and Numbers Authority (IANA) has as one of its functions the vetting of changes in the Internet root zone file.  IANA is a part of ICANN, the Internet Corporation for Assigned Names and Numbers.
> 2. ICANN has a zero-cost contract with the US government to execute this IANA function. In addition, the US government formally approves IANA's recommendations for changes in the root zone file before they are distributed to root zone operators and anycast servers.
> 3. Objections have been raised to US government involvement in this process on several grounds, including exclusivity and concerns of trust.  Objections have equally been raised to movement of the function to several international organizations.  
> 4. A solution is needed that meets several criteria: (1) protection of the root zone file from political or improper interference; (2) integrity, stability, continuity, security and robustness of operation; (3) widespread trust by Internet users in the organization executing this function and in its administrative mechanisms; and (4) agreement regarding accountability that is broadly perceived to be in the global public interest.   
> 5. At present, no such solution appears to exist. 
> _______________________________________________
> discuss mailing list
> discuss at 1net.org
> http://1net.org/mailman/listinfo/discuss

Dr. Ben Fuller
+264-61-224470  (O)    +264-88-63-68-05 (F)
ben at fuller.na             http://www.fuller.na
skype: drbenfuller

More information about the discuss mailing list