Download as PDF, PPTX
Uploaded byICANN
ICANN 52: Universal Acceptance
The document discusses the need for universal acceptance of new domain types and email addresses, highlighting the challenges faced by operating systems, email service providers, and users. It calls for the formation of a Universal Acceptance Steering Group to facilitate communication, outreach, and the development of best practices over an extended timeline. Key roles for the ICANN staff and community members are outlined, focusing on collaborative problem-solving and advocacy rather than policy development.
More Related Content
Similar to ICANN 52: Universal Acceptance
![ICANN Update [APRICOT 2015]](https://cdn.slidesharecdn.com/ss_thumbnails/apricotupdateapnic1425304176-150302191625-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
ICANN 52: Universal Acceptance
- 1. Universal Acceptance ICANN 52| 9 February 2015
- 2. | 2 q Introductionto Universal Acceptance q High priority issues q Marketing and communications approach q Call for a global community initiative q Next steps q Community feedback Agenda
- 3.
- 4.
- 5. New types ofdomains and email addresses break stuff.
- 6.
- 7. We are askingfor Universal Acceptance
- 8.
- 9.
- 11. public static booleanisValid(String email) { boolean result = true; try { InternetAddress emailAddr = new InternetAddress(email); emailAddr.validate(); } catch (AddressException ex) { result = false; } return result; } isValid(“[email protected]”): true isValid(“[email protected]”): true isValid(“[email protected]”): true isValid(“[email protected]”): true isValid(“伊昭傑@郵件.商務”): false // Correct // Correct // Correct // Not really // Definitely incorrect
- 12. public static booleanisValid(String email) { boolean result = true; try { InternetAddress emailAddr = new InternetAddress(email); emailAddr.validate(); } catch (AddressException ex) { result = false; } return result; } isValid(“[email protected]”): true isValid(“[email protected]”): true isValid(“[email protected]”): true isValid(“[email protected]”): true isValid(“伊昭傑@郵件.商務”): false // Correct // Correct // Correct // Not really // Definitely incorrect
- 15. What’s the problemagain?
- 16.
- 17. @ Operating systems Mail servers Routers Mailservice providers Security software Mail clients iPad Android phone Windows laptop
- 18.
- 19.
- 20.
- 21.
- 22.
- 23. Classic Communica,ons Plan Elements: Messaging Distribu,on MATCHING Audience Values
- 24.
- 25. The communica,on goal is to generate: awareness understanding action
- 26. … mul,plied through thousands of applica,ons, online services, systems
- 27. For example, sending a single email requires engaging an en,re support community Operating Systems ISPsEmail Server Software Routers Mail Clients Security Providers
- 28. UA Repository One solution Gettingpeople to look at it; trust it • Information • Resources • Solutions
- 29. each target audience has different interests § Business: effect on income & expenses § Ability to innovate § Looking for new opportunities § Reputation § In-house vs outsource practices in IT § Customer service § Cultural
- 30. each will respond to distribu,on channels § Social media § News § Individual corporate contacts § Formal public relations efforts § Trade Associations § Industry events
- 31. Road blocks to success § Who owns the problem? – Business owners – Hosting companies – Cloud service providers § What’s the incentive to fix it? – There could be significant expense – Return on investment is not readily apparent – Unclear ownership § Outreach and communications – Same issue as with new TLD availability – Most who have the problem are unaware
- 32.
- 33. Find the intersec,on of: CraIed by the industry to find the right • Message • Channel o ISPs o Browsers o Application Writers o Companies doing business on the Internet
- 34. Mobilising distribu,on channels § Social media: using the domain name industry and ICANN community to multiply messages through their own networks. § News stories: use contacts within global organizations and the ICANN community § Individual corporate contacts: using high-level contacts to get proper management attention § Hackathons § Offer to arrange meetings of PR firms
- 35. COMMUNICATIONS PLANNING Industry experts neededto: • Craft targeted messages • Match to audience Communications experts need to: • Develop distribution plan • Support & fund as necessary
- 37.
- 38. Call For AGlobal Community Initiative
- 39. Recommenda)on to ICANN Community on forma)on of Universal Acceptance Steering Group (UASG)
- 40. • A le?er has been draBed by workshop par)cipants to call on the ICANN community to join us on the crea)on of a Universal Acceptance Steering Group (UASG) • We are making the le?er available to the community today. Central are the following three points:
- 41. 1) The ICANN community should support the crea)on of a Steering Group to guide the iden)fica)on of topline issues and proposed solu)ons, as well as the crea)on and dissemina)on of best prac)ces and general outreach informa)on about Universal Acceptance.
- 42. 1)(con7nued) As this is a project that will take years to make progress on, the Steering Group would be a standing group whose membership may fluctuate over the years. ICANN should be prepared for the Steering Group to drive ac)on over the course of the next 10 years, though group leadership terms and structure should be re-‐evaluated every two years.
- 43. 2) ICANN staff should be the key coordinator in a formalized community effort on Universal Acceptance, and provide resources to the community in order to address this important issue.
- 44. 3) A call for general membership to the Steering Group will be announced at the ICANN Universal Acceptance mee)ng at ICANN52 in Singapore, pending community acceptance of our proposals. In short order following this mee)ng calls for Steering Group Chairs or Co-‐Chairs will then be made. The leadership chosen will be tasked to drive a further process to invite volunteers to join the group.
- 45. Role of community: The Universal Acceptance Steering Group (UASG) should be made up of ICANN community members as well as non-‐ICANN community experts. The UASG will provide guidance to the ICANN team as well as work alongside the ICANN team throughout the project. Ac)ve par)cipa)on as volunteers is expected from the community. The UASG will aim to include par)cipa)on as a mul)stakeholder group. The UASG and the UA Ini)a)ve is envisioned to be an advocacy group rather than a policy oriented group. As a result, weighted representa)on is not expected and par)cipa)on from various stakeholder groups are expected to change over )me and depending on the ac)vi)es and priori)es appropriate at various stages of the project.
- 46. Role of ICANN Staff: ICANN staff role is that of coordinator, catalyst and supporter and manager of the work streams. They are there to project manage and publish outcomes, and to provide budget to support the ini)a)ve. They should also act as a Secretariat for the UA Ini)a)ve. Though travel support to mee)ngs should not be required for Steering Group members, future research and outreach efforts may require financial support.
- 47. Work Streams • Universal Acceptance is a mul)-‐faceted issue, and the work of the UASG will be required to be broken into at least two work streams. Ini)al work stream recommenda)ons are: – High-‐priority issues – Communica)ons
- 48. Next Steps • Quick UASG next-‐steps meet-‐up 1-‐1:30PM Thursday February 12th SGT (UTC +8) outside of Padang • UASG Kickoff call 11AM Wednesday February 18th EST (UTC -‐5) • Sign up for UA-‐[email protected] for details at h?ps://mm.icann.org/mailman/lis)nfo/ua-‐discuss
- 49.
- 50.