Jump to content

Template:Article of the Week 2016/8: Difference between revisions

From ICANNWiki
Dustin Loup (talk | contribs)
Created page with "Universal Acceptance refers to the occurrence of users experiencing browser and email bugs when trying to use new gTLDs, including IDN|IDNs..."
 
Dustin Loup (talk | contribs)
No edit summary
Line 1: Line 1:
[[Universal acceptance|Universal Acceptance]] refers to the occurrence of users experiencing browser and email bugs when trying to use new [[gTLD|gTLDs]], including [[IDN|IDNs]].  Domain names in a TLD must be useable in applications regardless of the written script, length or newness of the TLD. In some instances, Internet users trying to use the newly delegated gTLDs, whose names may be many characters long and/or in non-Latin scripts, can experience bugs or the inability to access/register the sites.
[[Universal acceptance|Universal Acceptance]] refers to the occurrence of users experiencing browser and email bugs when trying to use new [[gTLD|gTLDs]], including [[IDN|IDNs]].  Domain names in a TLD must be useable in applications regardless of the written script, length or newness of the TLD. In some instances, Internet users trying to use the newly delegated gTLDs, can experience bugs or the inability to access/register the sites.


The four main shifts spurring the need for Universal Acceptance:
The four main shifts spurring the need for Universal Acceptance:

Revision as of 02:57, 22 February 2016

Universal Acceptance refers to the occurrence of users experiencing browser and email bugs when trying to use new gTLDs, including IDNs. Domain names in a TLD must be useable in applications regardless of the written script, length or newness of the TLD. In some instances, Internet users trying to use the newly delegated gTLDs, can experience bugs or the inability to access/register the sites.

The four main shifts spurring the need for Universal Acceptance:

  • Longer TLD Names
  • Non-Latin based TLDs
  • Rapid addition of TLDs
  • International Email