<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:477570503;
mso-list-type:hybrid;
mso-list-template-ids:194671774 269025281 269025283 269025285 269025281 269025283 269025285 269025281 269025283 269025285;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Dear colleagues,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">At the introduction this morning I mentioned the process led by the ccNSO to identify the four ccTLD members of the Coordinating Group. As background you might like to see the blog from the ccNSO chair that
talks about the selection process.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I promised to flag for the committee the report of the selection process: this is at
<a href="http://ccnso.icann.org/workinggroups/final-iana-stewardship-selectees-14jul14-en.pdf">
http://ccnso.icann.org/workinggroups/final-iana-stewardship-selectees-14jul14-en.pdf</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I hope this helps you understand the internal ccTLD process that was put in place to identity committee participation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Martin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Byron Holland [mailto:byron.holland@cira.ca]
<br>
<b>Sent:</b> 17 July 2014 19:03<br>
<b>To:</b> muduma@nira.org.ng; Martin Boyle; Xiaodong Lee (xl@cnnic.cn); Keith NZ<br>
<b>Subject:</b> Blog post - ccTLD candidate selection<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#1F497D">Dear Colleagues,</span><span lang="EN-CA" style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">There appears to be a little friction (seriously misplaced in my opinion) in our community regarding the slate of candidates that we put forward. I thought you might be interested in my blog on
the subject.</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Here’s the link: <a href="http://cirablog.ca/2014/07/moving-forward-with-internet-governance-reforms/">
http://cirablog.ca/2014/07/moving-forward-with-internet-governance-reforms/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D">And here is the text:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">If you read this blog regularly, or if you’re even tangentially involved in the Internet governance world, you know that 2014 is like no other year in the history of Internet governance. Since the National Telecommunication
and Information Administration’s (NTIA) announcement of its intent to transition out of its IANA role, contract, the topic has dominated global Internet governance discourse.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Apart from my day job as the head of the .CA registry, I’m the chair of the Country Code Name Supporting Organization (ccNSO), the entity within the ICANN ecosystem that represents the interests of country code top-level
domains (ccTLDs). As you can well imagine, I have been knee deep in the discussions around the transition of the accountability function the NTIA has played to this point for the IANA function.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">To oversee this process, ICANN has proposed a 27 member Coordinating Group. This group is to be comprised of representatives from IANA’s customers, like ccTLDs and gTLDs, and other key stakeholders. Four of those 27 seats
have been allocated by ICANN to ccTLDs, like .CA.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">It’s important to note that ICANN asked the ccNSO to select four ccTLDs, not ccNSO members, to join the Coordinating Group. To facilitate this level of inclusiveness, the ccNSO went to great lengths to ensure that the
call for applications was sent well beyond our community – through emails to every ccTLD in the IANA database, and by working with the Regional Organizations (ROs) to communicate with their members.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Let me note that I believe the process to choose the community representatives is critical, and not only because we need to ensure the best possible representation on this important group. Trust in the process is a crucial
component to ensuring acceptance of the outcomes. We need to get the process right if we are to be successful in our work.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">The ccNSO established a five member selection committee at the recent ICANN meeting in London and set out the criteria we felt that would enable the representatives to effectively represent the global ccTLD community.
I was a member of that Selection Committee, along with four other selected individuals, including ccNSO members, an RO-appointed member, and one non-ccNSO member.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">The communications regarding the call for nominations to this committee included the broadest outreach possible. We worked in many languages, and sent emails to every ccTLD in the IANA database. By working with the ROs
in our outreach, we were able to expand our reach to every corner of the globe. Every effort was made to make the communications as inclusive as possible, and I think the ccNSO Secretariat did an excellent job in this regard.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">We received about a dozen applications, and we were pleased that all of the nominees met the selection criteria and had the skill level and expertise to effectively represent the ccTLD community.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">We were faced with a very difficult task – balancing a wide variety of criteria to ensure effective representation of the diverse ccTLD community – 248 total worldwide. Among the considerations:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">High-level skills and expertise: the importance of the Coordinating Group cannot be underestimated, and to make sure ccTLDs receive the best possible representation on that group, we had set minimum standards
of skills and expertise for nominees.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">Time: we also had to ensure that the nominees had sufficient time to devote to this process, and that they had the support of their host organization to do so.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">Diversity of the ccTLD community: ccTLDs organize themselves in many different ways. Most (151, or 60 per cent) are members of the ccNSO. Those 151 represent 70 per cent of all registered ccTLD domain names.
Others are members of their respective ROs, and some are members of both the ccNSO and an RO. Others are non-aligned, choosing to not organize with any group(s) whatsoever. All of these groupings were considered in order to ensure the broadest possible reach
among the nominees.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">Geographic diversity: ICANN has five defined regions: Africa (AF), Asia/Australia/Pacific (AP), Europe (EU), Latin America/Caribbean (LAC), and North America (NA). From the Selection Committee’s report: “The
Committee members agreed that building on and in addition to the quality of the nominees on the shortlist, the geographic region of the nominee should be considered, also in the context of the composition of the full coordination group. Based on this consideration
the committee agreed that out of the four ccTLD members on the Coordination Group, no more than two should be from the same Geographic region.” With only four seats on the Coordinating Group, it was clear from the outset that true geographic representation
was not going to be possible. Furthermore, to ensure no one region would dominate the ccTLD representatives, the Selection Committee set a limit of no more than two nominees per region.”<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">Registry size: ccTLDs range in size from a few thousand domain names under management to a few with tens of millions under management.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">Governance structure: some ccTLDs, like .CA, are member-based and/or not-for-profits. Others are government departments, and some are privately held<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo2"><![if !supportLists]><span lang="EN-CA" style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-CA">Business models: while some ccTLDs are not-for-profits and generate income only to reinvest it in their host nation’s Internet community, others are run as for-profit business. There are a number of ccTLDs that
are subsidized by other entities, such as governments.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Given the criteria we had to balance, there were no ‘reserved’ seats for any one group. The fact is four seats only allowed us to ensure some – not all – of the criteria were met.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">The discussion was difficult and the outcome was not unanimous. We did, however, reach consensus. In paring this list down to the final four, we balanced the selection criteria – balance being the keyword here. Geographic
diversity is a good example of this – while there are five ICANN-defined geographic regions, we only had four seats on the Coordination Committee. Therefore, we knew from the outset not every objective would be fully realized. The goal was to balance all of
the criteria and produce a slate of nominees that would best b representative of the key interests of global ccTLD managers and operators. I am confident we have done that.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">There were many good candidates among the applicants, and making a final decision meant a long and challenging discussion. In the end, we put forward four names for which we reach agreed consensus – but not unanimity:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Martin Boyle, .UK, European Union region<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Keith Davidson, .NZ, Asia Pacific region<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Xiaodong Lee, .CN. Asia Pacific region<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Mary Uduma, .NG, Africa Region<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Did we meet the all of the criteria set out at the beginning of the process? No, but given the constraints we were facing – four seats to represent a community as large and diverse as ccTLDs – I have no hesitation in
endorsing each of them for their ability to be representative of the global ccTLD community – both ccNSO members and non-members – effectively. Opinions in the ccTLD community can be as diverse as the ccTLDs themselves. But, at the end of the day, we are all
ccTLD managers and operators who have a common interest in an excellent, high-performing and accountable IANA function.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">We made our best efforts to be as inclusive as possible. That spirit of inclusiveness will extend to the consultations and discussions in the broader ccTLD community as this process moves forward with specific transition
proposals.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">We are at the high water mark of the current Internet governance ecosystem. The work we are doing today will affect the ways in which the Internet develops in the future. We need to get the process right, and we need
to ensure that we are adhering to what are very important deadlines. With these four nominees, we are headed in the right direction.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="color:#1F497D"><o:p> </o:p></span></p>
</div>
</body>
</html>