| | At Large Membership and Civil Society Participation in ICANN |
|
| |
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
|
Commerce to Re-Award IANA to ICANN Without Considering Alternatives
|
Log in/Create an Account
| Top
| 4 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
Dateline: San Francisco
At the IETF meeting here in San Francisco not a soul can be found who believes that ICANN is competent to perform any of the technical functions of IANA.
There is a universal consensus here at the IETF meeting that the IANA functions should be stripped from ICANN as the result of repeatedly demonstrated incompetence.
I wonder what claims of competence were included in ICANN's bid to NTIA, or rather NOAA? Are there any reporters out there willing to pursue a FOIA request to take a look at what ICANN submitted?
And come to think of it - NOAA?!! Pushing the IANA contract through the National Oceanic and Atmospheric Administration does have a strong and foul stench of laundering.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
|
| Starting Score: |
2 |
points |
| Extra 'Informative' Modifier |
|
0 |
|
| Total Score: |
|
2 |
|
|
|
|
Sorry, but this is utter garbage. "Anonymous" is speaking about something that never happened. I am posting from IETF meeting (and I'm putting my name on this post...).
- The IANA discussion is going to happen about 18 hours after I post this... Saying that there was "universal consensus" when the discussion is in the future is an interesting trick.
- In off-line talks, I know lots of active IETF folks who think ICANN is competent to perform IANA. Many of us would rather that ICANN wasn't doing it (for many reasons), but that is radically different than saying that they are not competent.
- Fully agree about the NOAA stench. But that is unrelated to the preceding lies about the views on competence.
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
"the IANA function" has several components. One part is the IP address allocation part, another is figuring out who gets TLD slots (with the particularly troublesome question of who gets to run ccTLDs.) The part that I suspect is most interesting to the IETF is the part of handling the assignment of various protocol numbers.
I have not been able to get a clear feel about how much this costs ICANN to handle. The raw number of hours of labor might be interesting to know, particularly if the IETF were to consider having somebody other than ICANN do the work.
From the IETF point of view I don't see that there has been any problem in assigning the various numbers - we can look at ICANN's status report to NTIA to get a listing of what was done. I have not heard anybody complaining about number clashes.
The more interesting question for the IETF is whether it could get better number services from some other body or perhaps the IETF's own secretariat. However, the IETF is getting a good deal from ICANN - whatever the cost to ICANN, the cost to the IETF for protocol number assignments is zero. And given the IETF's prospective financial distress, ICANN certainly represents a bargain.
As for the NOAA part - I'm sure that there must be some strange bureaucratic reason why it was issued by NOAA rather than NTIA. I wish somebody would explain why a zero-dollar purchase couldn't be handled by NTIA the same way it buys magazine subscriptions.
|
|
|
|
[ Reply to This | Parent
]
|
| - 1 reply beneath your current threshold.
|
Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|
