Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

ICANN 52: Universal Acceptance

Wird geladen in …3
×

Hier ansehen

1 von 50
1 von 50

Weitere Verwandte Inhalte

Ähnliche Bücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

Ähnliche Hörbücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

ICANN 52: Universal Acceptance

  1. 1. Universal Acceptance ICANN 52 | 9 February 2015
  2. 2. | 2 q  Introduction to 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. 3. Introduction to Universal Acceptance
  4. 4. High Priority Issues
  5. 5. New types of domains and email addresses break stuff.
  6. 6. 実例.みんな example.photography Борис@почта.пример.рф
  7. 7. We are asking for Universal Acceptance
  8. 8. 実例.みんな example.photography Борис@почта.пример.рф
  9. 9. ?
  10. 10. public static boolean isValid(String email) { boolean result = true; try { InternetAddress emailAddr = new InternetAddress(email); emailAddr.validate(); } catch (AddressException ex) { result = false; } return result; } isValid(“address@example.com”): true isValid(“address@example.network”): true isValid(“address@xn--5nqv22n.xn--lhr59c”): true isValid(“address@example.isnotarealtld”): true isValid(“伊昭傑@郵件.商務”): false // Correct // Correct // Correct // Not really // Definitely incorrect
  11. 11. public static boolean isValid(String email) { boolean result = true; try { InternetAddress emailAddr = new InternetAddress(email); emailAddr.validate(); } catch (AddressException ex) { result = false; } return result; } isValid(“address@example.com”): true isValid(“address@example.network”): true isValid(“address@xn--5nqv22n.xn--lhr59c”): true isValid(“address@example.isnotarealtld”): true isValid(“伊昭傑@郵件.商務”): false // Correct // Correct // Correct // Not really // Definitely incorrect
  12. 12. What’s the problem again?
  13. 13. Universal Acceptance
  14. 14. @ Operating systems Mail servers Routers Mail service providers Security software Mail clients iPad Android phone Windows laptop
  15. 15. Universal Acceptance Repository
  16. 16. English explanations Code samples Case studies
  17. 17. In progress at ua.thedna.org
  18. 18. Marketing And Communications Approach
  19. 19. Universal Acceptance: Communications / Outreach
  20. 20. Classic  Communica,ons  Plan  Elements:   Messaging   Distribu,on   MATCHING Audience   Values  
  21. 21. a  complicated  proposi,on  
  22. 22. The  communica,on  goal  is  to  generate:   awareness understanding action
  23. 23. …  mul,plied  through  thousands  of  applica,ons,   online  services,  systems    
  24. 24. For  example,  sending  a  single  email   requires  engaging  an  en,re  support  community   Operating Systems ISPsEmail Server Software Routers Mail Clients Security Providers
  25. 25. UA Repository One solution Getting people to look at it; trust it •  Information •  Resources •  Solutions
  26. 26. 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
  27. 27. each  will  respond  to  distribu,on  channels   § Social media § News § Individual corporate contacts § Formal public relations efforts § Trade Associations § Industry events
  28. 28. 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
  29. 29. craIing  communica,ons  solu,ons  
  30. 30. 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
  31. 31. 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
  32. 32. COMMUNICATIONS PLANNING Industry experts needed to: •  Craft targeted messages •  Match to audience Communications experts need to: •  Develop distribution plan •  Support & fund as necessary
  33. 33. Thank  You  
  34. 34. Call For A Global Community Initiative
  35. 35. Recommenda)on  to  ICANN   Community  on  forma)on  of   Universal  Acceptance  Steering   Group  (UASG)  
  36. 36. •  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:  
  37. 37. 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.    
  38. 38. 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.      
  39. 39. 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.      
  40. 40. 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.    
  41. 41. 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.  
  42. 42. 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.    
  43. 43. 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  
  44. 44. 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-­‐discuss@icann.org  for  details  at   h?ps://mm.icann.org/mailman/lis)nfo/ua-­‐discuss  
  45. 45. Next Steps
  46. 46. Community Feedback

×