Talk:ICANN

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


Citation needed[edit]

What is with all the "citation needed" signs? This article should be about one of the most (if not just the most) open organizations on the planet. Is there so little we officially know about it? I understand that there are a lot of unofficial rumors and pieces of information about it, but why is there so little of it that is backed up by official sources? -- T (unknown date)

On new section "Proposed Elimination of Public DNS Whois"[edit]

This section just appeared in the ICANN entry, and while I've corrected several aspects of it, it probably needs more work to achieve neutral tone. Also, it may be a fairly transitory issue, hence wondering if it warrants inclusion in the main entry at all. fyi --TcomptonMA 10:39, 23 September 2013 (UTC) — Preceding unsigned comment added by TcomptonMA (talkcontribs)

Thanks for making the edit. IMO this raises serious issues regarding ICANN whether or not this time it is transitory or not. LookingGlass (talk) 18:22, 24 September 2013 (UTC)[reply]

UDRP circumvention[edit]

Hi, there have been several edits to the article where the contributor attempts to note a "potential conflict-of-interest" in cases where multiple registrars are operated by the same corporation. The contributions were removed, and I ask that such notes be protected. CHeers126.209.0.225 (talk) 11:28, 18 October 2017 (UTC) Again, requesting abovementioned notes be protected. Operation of multiple Registries increases likelyhood of undetected cybercrime, i.e. Domain hijacking. Today, May 25th, is rollout of EU GDPR which likely results in concealing or limiting access to DNS Records, WHOIS. This amplifies the need for protection.[1] — Preceding unsigned comment added by 126.161.163.165 (talk) 11:59, 25 May 2018 (UTC)[reply]

References

ICANN/VeriSign corruption scandal[edit]

An experienced Wikipedia editor should probably add something about the $20M bribe ICANN is taking to let VeriSign hike dotcom TLD prices even though as a registry it does very little actual work that provides the value of domains.--Xaekai (talk) 20:55, 11 February 2020 (UTC)[1] [2][reply]

References

  1. ^ "ICANN Wants to Let VeriSign Raise Prices on .Com Domains". Slashdot. Retrieved 11 February 2020.
  2. ^ "ICANN Allows .COM Price Increases, Gets More Money". Hacker News. Retrieved 11 February 2020.

Archive page created[edit]

As this Talk page contained many old sections that either had been addressed or were no longer relevant (ex. they referred to sections of the page that have been changed), I have moved those old sections to a new archive page following the H:ARC manual process. - Dyork (talk) 02:59, 11 November 2020 (UTC)[reply]

Obsolosence[edit]

The Oversite section to the Internet Assigned Numbers Authority states:

In August 2016 ICANN incorporated Public Technical Identifiers, a non-profit affiliate corporation in California, to take over the IANA functions once the current contract expired at the end of September.[55][56] The Department of Commerce confirmed that its criteria for transitioning IANA Stewardship to the Internet multistakeholder community had been met, and that it intended to allow its contract with ICANN to expire on September 30, 2016, allowing the transition to take effect.[57][58][59] On October the contract between the United States Department of Commerce and ICANN to perform the IANA functions was allowed to expire and the stewardship of IANA functions was officially transitioned to the private-sector.[60][61]

This suggests that ICANN no longer manages IANA. Is that right? Should this page get updated? Liberty5651 (talk) 19:00, 25 May 2021 (UTC)[reply]

  • @Liberty5651: No, it's a bit more complicated. ICANN still has management oversight of IANA. What happened in in 2016 was that the US Dept of Commerce's NTIA removed itself from any management role in the root zone of DNS. Prior to 2016, NTIA had a role in the IANA management through its contract with ICANN. After the "IANA stewardship transition" in September 2016, NTIA was out of the loop of IANA management. ICANN was now fully in control of the IANA function. As part of this transition, ICANN created PTI as an affiliate to perform the actual operations of the "IANA function" (see IANA About Us). But as outlined in the "IANA Naming Function Agreement", ICANN "will continue to serve as the Internet Assigned Numbers Authority (“IANA”) functions operator" with PTI serving as the contractor to actually operate the IANA functions. You could think of it as ICANN doing the higher-level management and PTI doing the actual execution. I hope that helps! - Dyork (talk) 02:15, 26 May 2021 (UTC)[reply]

A Commons file used on this page or its Wikidata item has been nominated for speedy deletion[edit]

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for speedy deletion:

You can see the reason for deletion at the file description page linked above. —Community Tech bot (talk) 14:22, 15 April 2022 (UTC)[reply]

A Commons file used on this page or its Wikidata item has been nominated for deletion[edit]

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 15:52, 15 April 2022 (UTC)[reply]

Kumar[edit]

tjtj — Preceding unsigned comment added by 2409:4055:2E9C:6BE2:1BC3:1234:7128:9269 (talk) 04:14, 23 March 2024 (UTC)[reply]