Summary

  • ICANN says its Universal Acceptance curriculum now involves six universities and has entered 23 courses, reaching 1,063 students at the initial institutions. That is a growing classroom, with India, Zimbabwe and Bolivia joining the first three countries.
  • The software test sits elsewhere. ICANN separately measures whether real systems handle internationalized names and email addresses. The useful governance bridge is a visible path from lessons and assessed exercises to reproducible tests and repaired products.

The registrar of attendance meets the registration form

A thousand students learn that an email address can contain a script their grandparents use. A sign-up form rejects it in half a second. The form wins that encounter. ICANN’s 27 October account of its Universal Acceptance curriculum makes the scale of its educational bet concrete: six participating universities, 23 courses containing UA material and 1,063 students reached across the initial institutions. The three new universities are in India, Zimbabwe and Bolivia. Their addition turns a February pilot into something more geographically dispersed. It also sharpens the question a university prospectus cannot answer for an Internet user: what changes in the code?

Universal Acceptance, or UA, asks software to handle valid domain names and email addresses across scripts, lengths and languages. The address has to survive several encounters with a product: input boxes, validators, stored records, messages and the return trip to the screen. A developer can understand the principle and still inherit a library that discards the string. A project manager can approve a feature list that never asks for an internationalized address in testing. Governance here is the quiet power to define “works” in a software release.

ICANN launched the program in February 2026 with partners in Bahrain, Mexico and India. Its training page describes twelve modules on Internationalized Domain Names, Email Address Internationalization and UA. Universities can fold them into existing degrees or offer a focused course; ICANN provides the material and support without a fee. The program flyer sketches a more operational bargain: two to three days of faculty training, up to two years of technical support and quarterly conversations. That is an institutional route into a syllabus, with teachers able to return to the subject when a first lecture meets an actual lab machine.

One ledger counts teaching; another counts broken systems

The October update counts institutions, courses and students reached. Those are legitimate measures of whether ICANN can get a technical issue into classrooms. It publishes no course-level inventory, completion rate, assessment results or software deployments from this cohort. Asking for those records is a practical editorial question. If a student leaves a course able to write a test that accepts a valid address, preserves it and sends a message to it, the educational program has produced something an engineer can inspect. A seat count cannot show that outcome by itself.

ICANN already operates a separate UA-readiness evaluation surface. It describes tests of applications, browsers, mail systems and websites; a roadmap for registries and registrars; and a public channel for reporting failures. Its EAI survey examines mail exchangers serving second-level domains in generic top-level domains. On the measure published there, the share of domains with UA-ready mail servers rose from about 20% in 2022 to 29% in 2026. That figure describes a particular slice of deployed mail infrastructure. It cannot be assigned to six universities, and ICANN makes no such causal claim. It does show the kind of observable system behavior that education is ultimately supposed to help change.

The two records can meet without turning every graduate into a laboratory experiment. A course can publish its test cases, explain which libraries or application flows students exercised and report where a valid identifier failed. An institution can show whether its software engineering assessment asks students to keep internationalized addresses intact through input, storage and email handling. ICANN can then report adoption of those practical exercises alongside institutional reach. The next measurement is less photogenic than a signing ceremony. It is also closer to the user with a rejected address.

Who owns the handoff?

ICANN supplies curriculum and training. Universities decide how to teach and assess it. Employers, maintainers and procurement teams decide which tests enter production software. No one actor can command the entire chain. The program’s strength is precisely that it changes the default knowledge of people who will later make those choices. Its weak point is the gap between a course catalogue and an acceptance test.

An institution can announce a multilingual Internet while its own login form still has a private definition of a valid address. A graduate can know the acronym and never see a failing test. ICANN’s public evaluation tools give this campaign a better finish line: named failure modes, reproducible checks and fixes that survive the next release. Six universities are a credible start for teaching. The sign-up form is still the final examiner.

Sources