Universal Acceptance

Add links
From Wikipedia, the free encyclopedia

Universal Acceptance (UA) is a term coined by Ram Mohan to represent the principle that every top-level domain (TLD) should function within all applications regardless of script, number of characters, or how new it is.[1]

Historically, there were a limited number of TLDs available in strings of two or three Latin-script characters. This began to change in 2000, when ICANN introduced new generic top-level domains (gTLDs) that were longer than three characters, such as .info and .museum. ICANN began to address these issues through initiatives such as creating a Universal Acceptance Toolkit[2] in 2006, which provided reference code to software developers on how to cater for all TLDs correctly.

In 2010, the first internationalised domain names (IDNs), or domain names using non-Latin characters, were introduced. In 2013, ICANN's New gTLD Program introduced over 1,000 new gTLDs to its root.[3] This expansion of the Domain Name System’s Root Zone further exacerbated challenges associated with universal acceptance of these domain names. For the principles of Universal Acceptance to be realized, all valid domain names and email addresses must be accepted, validated, stored, processed and displayed correctly and consistently by all Internet-enabled applications, devices and systems.[4]

Universal Acceptance Steering Group[edit]

In February 2015, Ram Mohan founded the Universal Acceptance Steering Group (UASG) at the ICANN52[5] meeting in Singapore, following efforts at organizing the IDN community at the ICANN IDN symposium in Dubai. The first face to face meeting of the UASG was held at the ICANN53[6] meeting in Buenos Aires. The UASG has grown into a community-led program, supported by ICANN, aimed at facilitating the adoption of Universal Acceptance principles by the industry.[7]

Mohan's Laws of Universal Acceptance[edit]

In 2002[citation needed], Ram Mohan, then CTO of the .INFO TLD, experienced the first instances of Universal Acceptance problems,[8] and crafted three laws that appeared valid in the domain name space:

  1. An old TLD will be accepted more often than a new TLD.
  2. An ASCII-only TLD will be accepted more than an IDN TLD.
  3. A two or three letter TLD will be accepted more often than a longer ccTLD or gTLD.

As of 2024, these laws appear to still hold true.[9] The success of Universal Acceptance would result in these laws becoming obsolete.

Universal Acceptance of popular web browsers[edit]

One of the primary ways of interfacing with the Internet is through web browsers. For this reason, the UASG commissioned a report on the performance of major browsers in the treatment and acceptance of 17 different domain names registered for the purpose of providing test cases for UA readiness.[10][11]

The study found that desktop browsers generally performed well, but only Internet Explorer performed as expected. Common problems among the other browsers included the failure to properly render the URLs in the tab title bar and failing to treat an ideographic full stop as a delimiter. On mobile platforms, the results of the tests were much more varied, with the same browsers performing differently based on the operating system, with one of the most common problems being the proper display of Unicode URLs.

The study concluded that developers are making progress in making browsers UA Ready, but there is more work to do on every browser except Internet Explorer, a browser that has been discontinued.

Email address internalization[edit]

Internationalized email address is also part of Universal Acceptance Steering Group, where Email Service providers are motivated to start providing email address for IDNs and also engage them to solve issues related to interoperability with legacy systems. Downgrading is not recommended using punycode however providing ASCII Alias email address with EAI is the recommended practice. Aliasing as downgrading technique is being practiced by BSNL,[12] which used XgenPlus[13] email solution.

Internationalized Domain Names (IDNs)[edit]

Internationalized Domain Names (IDNs) are linked to Universal Acceptance, because TLDs in local languages are always more than 3 letters long, and often do not work well in browsers, emails and other internet applications. One of the earliest groups recognizing the importance of IDNs and problems with Universal Acceptance was the Arabic Script IDN Working Group (ASIWG). Operated by Afilias' Ram Mohan, ASIWG aims to develop a unified IDN table for the Arabic script, and is an example of community collaboration that helps local and regional experts engage in global policy development, as well as technical standardization[14] [15].It is reasonable to infer, therefore, that the usage growth could have been even more significant if DNS was available in Arabic characters.

Leadership at Universal Acceptance Steering Group[edit]

Leaders for UASG are chosen every two years by vote. In February 2015, Ram Mohan was elected chair, and Edmon Chung, Richard Merdinger and Mark Svancarek were elected vice chairs. In February 2017, Ram Mohan was reelected Chair, with the same slate as 2015. In March 2019, Ajay Data was elected[16] Chair and Dusan Stojicevic, Mark Svancarek and Dennis Tan Tanaka were elected vice chairs. In 2021 Ajay Data was reelected Chair of along with Dr. U.B. Pavanaja and Abdalmonem Galila as vice chairs.[17]

Working groups[edit]

In 2019, UASG created working groups[18] with community leaders and volunteers to better manage the groups works.

  • Technology Working Group
  • Email Address Internationalization
  • Communications
  • Measurement
  • Local Initiatives

UA Day[edit]

In 2022, ICANN and the UASG announced their intention to celebrate the UA Day, starting with the first one on 28 March 2023.

References[edit]

  1. ^ "ICANN - Universal Acceptance". ICANN. February 25, 2012.
  2. ^ "ICANN Releases Beta-3 Version of TLD Verification Code". ICANN. Retrieved March 21, 2023.
  3. ^ "First IDN ccTLDs available". ICANN. May 5, 2010.
  4. ^ "UASG Quick Guide" (PDF). Universal Acceptance Steering Group. Retrieved December 14, 2017.
  5. ^ "Home | ICANN52 | Singapore". archive.icann.org. Retrieved 2019-06-25.
  6. ^ "Universal Acceptance Steering Group Workshop | ICANN53 | Buenos Aires". archive.icann.org. Retrieved 2019-06-25.
  7. ^ "ICANN - Universal Acceptance". ICANN. February 25, 2012.
  8. ^ Mohan, Ram. "More problems crop up with universal acceptance of top level domains". CircleID. Retrieved 19 February 2020.
  9. ^ https://uasg.tech/wp-content/uploads/documents/UASG025-en-digital.pdf [bare URL PDF]
  10. ^ "Universal Acceptance of Popular Browsers" (PDF). Universal Acceptance Steering Group. Retrieved December 14, 2017.
  11. ^ "Use Cases for UA Readiness Evaluation" (PDF). Universal Acceptance Steering Group. Retrieved December 14, 2017.
  12. ^ "XgenPlus empowers BSNL to host linguistic domains". www.aninews.in. Retrieved 2018-03-06.
  13. ^ "Data XGen Launches Linguistic Email ID Service In India - CXOtoday.com". www.cxotoday.com. Retrieved 2018-03-06.
  14. ^ "Internet Governance: Challenges and Opportunities for the ESCWA Member Countries"" (PDF). Economic and Social Commission for Western Asia (ESCWA), United Nations. 15 June 2009.
  15. ^ "EXPERT GROUP MEETING ON THE USE OF ARABIC SCRIPT IN DOMAIN NAMES" (PDF). UN ESCWA Arabic Script Languages. May 28, 2008.
  16. ^ "UASG Elects New Chair". Universal Acceptance Steering Group. 15 March 2019.
  17. ^ UASG. "UASG Leaders". Universal Acceptance Steering Group (UASG). Retrieved 2022-06-14.
  18. ^ UASG. "Working Groups". Universal Acceptance Steering Group (UASG). Retrieved 2022-06-14.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Universal_Acceptance&oldid=1213242113"