AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
ALAC Liaisons and Representatives
At-Large Review Implementation Plan Development
Page History
...
# | Measure of End-User Trust | Source | Anticipated Difficulties in | 3-year target |
---|---|---|---|---|
End-User Confusion | ||||
1.1 | Success in reaching the intended information supplier using domain names | Survey of end-users; SEO research | Note 1 | Neutral or increase |
1.2 | Accidental landing at unintended destinations | Survey of end users, SEO analytics | Note 1 Selective sampling of analytics may help determine the success of typo-squatting or other unintended destinations | Neutral or decrease |
1.3 | Volume of redundant or defensive domains (ie, multiple domains pointing to the sam destination) | Survey of registrants | Note 2 | Neutral or decrease |
1.4 | Dead-end domains (registered but do not resolve) | Registry data + automated sampling | Note 3 | Proportion relative to total domains should decrease |
1.5 | Numbers of complaints received by ICANN regarding improper use of domains | ICANN | Supplements GNSO metric 1.9 by assessing volume of end-user complaints (which may not come from name owners or result in URS/UDRP action) | |
Growth in use of both domain-based and non-domain-based alternatives for Internet resource access | ||||
2.1 | Relative preference of domain names versus search engines for end-user general Internet use | Survey of end users; SEO analytics | Note 1 | Note 4 |
2.2 | Growth in use of corporate pages (such as Facebook or Google+) | Market research | Ie, ComScore | Note 4 |
2.3 | Growth in use of QR codes | Market research | ie, ScanLife | Note 4 |
2.4 | Growth in use of URL shortening services | Market research | Note 4 | |
2.5 | Growth in registrations in ccTLDs relative to gTLDs | Registry data | Note 3 | A significant increase in the use of ccTLDs could mean reduced trust in generic TLDs. |
Complaints to, and action taken by, police, regulatory agencies and advocacy groups | ||||
3.1 | Number of consumer complaints to government agencies related to confusing or misleading domain names | Government regulatory agencies | Establishing relationships with consumer protection and regulatory agencies may be difficult to initiate; however ICANN ought to have such relationships in place anyway, either directly or through GAC representatives | Proportion relative to total domains should decrease |
3.2 | Number of complaints to police agencies alledging fraud or misrepresentation based on domain names | Police agencies | ICANN already has existing communications with LEA groups. Supplements GNSO metrics 1.15 and 1.16 buy adding complaints as well as remedial action | |
Transparency of contact information and domain-allocation policies for all gTLDs | ||||
4.1 | How many gTLD registries have privacy policies which are clearly and easily accessible by end users | Registry websites | Manual auditing | As many as possible |
4.2 | How many gTLD registries have allocation policies which are clearly and easily accessible by end users | Registry websites | Manual auditing | As many as possible See Note 5 |
4.3 | How many registries disclose end-user information regarding their codes of conduct for sub-domain owner/operators | Registry websites | Manual auditing | As many as possible See Note 5 |
Accuracy of new gTLD promotion to end users | ||||
5.1 | How many complaints are received by ICANN related to confusion or misunderstanding of TLD functions | ICANN | ||
5.2 | How many registries uphold to their Public Interest Committments | ICANN, independent audit | Whether or not PICs are enforceable, they are public and likely indicate how each registry is marketed | |
5.3 | How many registries are subject to Compliance investigation based on breaches of RRA related to objectives or PICs | ICANN | ||
Technical issues encountered (including application support) | ||||
6.1 | Are end-user software applications capable of implementing all of the new gTLDs; Can browsers and DNS clients in end-user systems resolve all new gTLDs | Audit | All major browsers and operating systems should be able to resolve news gTLDs, including IDNs | |
6.2 | Which browsers or other end-user applications require plugins or user-installed enhancements in order to use new gTLDs | Audit | Support should be native rather than as an add-in |
...