Jump to content

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

From ICANNWiki
Dustin Loup (talk | contribs)
No edit summary
Dustin Loup (talk | contribs)
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<div style="font-size:1rem;">
<div style="font-size:.9rem;">
[[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.
[[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.



Latest revision as of 16:28, 23 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