Skip to main content

Why I Love the International Office Strategy

I am proud of many things the ICANN organization has put in place since I've been at ICANN for nearly two years now. One that I am very excited about is our international office strategy.

The international office strategy recognizes that stakeholders in different parts of the world have different needs.

Before this, the org didn't have a formal strategy for supporting the diverse needs of our stakeholders around the world. We had three hubs, but now we've taken it to the next level with more locations around the world. This means we can better serve your needs and improve the multistakeholder experience.

As a reminder, we now have five regional offices, headed up by managing directors who are in charge of regional strategic plans. They are:

  • Los Angeles – headquarters, also serving North America
  • Brussels – serving Europe, led by Jean-Jacques Sahel
  • Istanbul – serving the Middle East and Africa, led by Nick Tomasso
  • Montevideo – serving Latin America and the Caribbean, led by Rodrigo de la Parra
  • Singapore – serving Asia Pacific and Oceania, led by Jia-Rong Low

We also have engagement centers in:

  • Beijing – led by Jian-Chuan Zhang
  • Geneva – led by Tarek Kamel
  • Nairobi – led by Pierre Dandjinou
  • Washington, D.C. – led by Duncan Burns until he leaves 22 March, then Jamie Hedlund

We also have strategic partnerships in Asunción, Cairo, and Seoul. We chose these locations deliberately to help us further support specific stakeholder needs and to ensure that ICANN is active in matters that impact our mission.

This enhanced operating model keeps us aligned so that all regional plans are more consistent and we leverage best practices. The managing directors meet regularly as a group to coordinate.

What this means for you is that we're more efficient in delivering our services. We leverage global frameworks and blueprints to avoid reinventing the wheel. We discuss and share regional strategic plans and plan for trends that we are seeing – both globally and locally. It means we plan security on a local level for the well-being of our people and the community. It means we are "one ICANN," but have regional flexibility. Each office is unique.

Now you can see why I am so excited about this! I think this strategy will take ICANN to the next level. We are stable and mature. We have global standards and processes in place.

As you can imagine, this is a big change for us as an org, and we'll continue to improve this matrixed way of working. I encourage you to continue getting involved in your regional strategies and reaching out to your regional leader.


    oscar daddy okeke  09:56 UTC on 23 March 2018

    Good news, i have being reading up about ICANN since i had about them in the course of my project,after discussing with friends i must say i am very impressed at the achievement of ICANN. I would want that ICANN should take a look at the Nigeria market, the above strategy would work better there.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."