| | At Large Membership and Civil Society Participation in ICANN |
|
| |
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
|
A Public Private Partnership
|
Log in/Create an Account
| Top
| 17 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
|
Your statement that "ICANN's role in IANA is derived soleley and exclusively by virtue of its role as provider under a purchase order from the US National Oceanic and Atmospheric Administration (a branch of the US Dept of Commerce)" is not accurate. Remember that the Internet Architecture Board designated ICANN to perform the technical IANA functions in RFC 2860. <http://www.ietf.org/rfc/rfc2860.txt> [ietf.org] And don't forget the December 1998 agreement between ICANN and USC, by which USC handed the IANA over to ICANN. (This agreement, apparently, was endorsed by NTIA.)
|
|
|
|
[ Reply to This | Parent
]
|
|
|
|
ICANN's Authority Comes from More than One Place
by George Matrox
|
|
|
|
|
What you are indicating is that the sources of authority for IANA are even more muddy and are, in fact, potentially contradictory.
Suppose DoC sends IANA to someone else and the IAB doesn't go along.
This is the kind of muddy thinking that has filled ICANN since the outset.
|
|
|
|
[ Reply to This | Parent
]
|
| |
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
|
