<html 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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
h4
{mso-style-priority:9;
mso-style-link:"Heading 4 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-priority:9;
mso-style-link:"Heading 4";
font-family:"Calibri",sans-serif;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1651249398;
mso-list-template-ids:-896336410;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">For your information (see <a href="https://www.icann.org/resources/board-material/resolutions-2019-01-27-en#2.c">
https://www.icann.org/resources/board-material/resolutions-2019-01-27-en#2.c</a>):<o:p></o:p></span></p>
<h4><span style="font-family:Symbol">·</span> GAC Advice: Barcelona Communiqué (October 2018)<o:p></o:p></h4>
<p>Whereas, the Governmental Advisory Committee (GAC) met during the ICANN63 meeting in Barcelona, Spain and issued advice to the ICANN Board in a
<a href="https://www.icann.org/en/system/files/correspondence/gac-to-icann-25oct18-en.pdf">
communiqué</a> on 25 October 2018 ("Barcelona Communiqué").<o:p></o:p></p>
<p>Whereas, the Barcelona Communiqué was the subject of an <a href="https://gac.icann.org/sessions/gac-and-icann-board-conference-call-regarding-icann62-communique">
exchange</a> between the Board and the GAC on 28 November 2018.<o:p></o:p></p>
<p>Whereas, in a 20 December 2018 <a href="https://www.icann.org/en/system/files/correspondence/ismail-to-chalaby-botterman-20dec18-en.pdf">
letter</a>, the GAC provided additional clarification of language contained in the Barcelona Communiqué Annex titled Follow-up to Original Joint Statement by ALAC and GAC (Abu Dhabi, 2 November 2017).<o:p></o:p></p>
<p>Whereas, in a 21 December 2018 <a href="https://www.icann.org/en/system/files/correspondence/drazek-et-al-to-icann-board-21dec18-en.pdf">
letter</a>, the GNSO Council provided its feedback to the Board concerning advice in the Barcelona Communiqué relevant to generic top-level domains to inform the Board and the community of gTLD policy activities that may relate to advice provided by the GAC.<o:p></o:p></p>
<p>Whereas, the ICANN organization published a <a href="https://www.icann.org/en/system/files/files/implementation-memo-two-character-ascii-labels-22jan19-en.pdf">
memorandum</a> and <a href="https://www.icann.org/en/system/files/files/historical-overview-two-character-ascii-labels-22jan19-en.pdf">
historical briefing paper</a> providing clarification regarding the development and evolution of ICANN organization's procedure for the release of two-character labels at the second level and the standard framework of measures for avoiding confusion with corresponding
country codes.<o:p></o:p></p>
<p>Whereas, the Board developed a scorecard to respond to the GAC's advice in the Barcelona Communiqué, taking into account the dialogue between the Board and the GAC, the clarification letter provided by the GAC Chair, the information provided by the GNSO
Council, and the memorandum and briefing paper released by the ICANN org.<o:p></o:p></p>
<p>Whereas, the Board has considered the <a href="https://www.icann.org/en/system/files/files/resolutions-panamacity62-gac-advice-scorecard-16sep18-en.pdf">
previously deferred GAC advice</a> regarding two-character country codes at the second level from the Panama Communiqué, and has included a response in the current scorecard "GAC Advice – Barcelona Communiqué: Actions and Updates (25 January 2019)".<o:p></o:p></p>
<p>Resolved (2019.01.27.18), the Board adopts the scorecard titled "<a href="https://www.icann.org/en/system/files/files/resolutions-barcelona63-gac-advice-scorecard-27jan19-en.pdf">GAC Advice – Barcelona Communiqué: Actions and Updates (25 January 2019)</a>"
in response to items of GAC advice in the Barcelona Communiqué and the Panama Communiqué.<o:p></o:p></p>
<h4><a name="2.c.rationale"></a><em><span style="font-family:"Calibri",sans-serif">Rationale for Resolution 2019.01.27.18</span></em><o:p></o:p></h4>
<p>Article 12, Section 12.2(a)(ix) of the ICANN Bylaws permits the GAC to "put issues to the Board directly, either by way of comment or prior advice, or by way of specifically recommending action or new policy development or revision to existing policies."
In its Barcelona Communiqué (25 October 2018), the GAC issued advice to the Board on: two-character country codes at the second level and protection of names and acronyms of Intergovernmental Organizations (IGOs) in gTLDs. The GAC also provided a follow-up
to previous advice GDPR and WHOIS, the Dot Amazon applications, protection of the Red Cross and Red Crescent designations and identifiers, and a follow-up to the joint statement by ALAC and GAC (Abu Dhabi, 2 November 2017). The ICANN Bylaws require the Board
to take into account the GAC's advice on public policy matters in the formulation and adoption of the polices. If the Board decides to take an action that is not consistent with the GAC advice, it must inform the GAC and state the reasons why it decided not
to follow the advice. Any GAC advice approved by a full consensus of the GAC (as defined in the Bylaws) may only be rejected by a vote of no less than 60% of the Board, and the GAC and the Board will then try, in good faith and in a timely and efficient manner,
to find a mutually acceptable solution.<o:p></o:p></p>
<p>The Board is taking action today on all items in the Barcelona Communiqué, including the items related to two-character country codes at the second level as well as protections of IGOs. The Board is also taking action on the items regarding two-character
country codes at the second level from the Panama Communiqué, consideration of which had been previously deferred.<o:p></o:p></p>
<p>The Board will continue to defer consideration of five items from the San Juan Communiqué, including: four advice items related to GDPR and WHOIS and one advice item related to IGO reserved acronyms, pending further discussion with the GAC. The Board will
consider if further action is needed following these discussions.<o:p></o:p></p>
<p>The Board's actions are described in the <a href="https://www.icann.org/en/system/files/files/resolutions-barcelona63-gac-advice-scorecard-27jan19-en.pdf">
scorecard dated 25 January 2019</a>.<o:p></o:p></p>
<p>In adopting its response to the GAC advice in the Barcelona Communiqué, the Board reviewed various materials, including, but not limited to, the following materials and documents:<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.0pt">Panama Communiqué (28 June 2018): <a href="https://www.icann.org/en/system/files/correspondence/gac-to-icann-28jun18-en.pdf">
https://www.icann.org/en/system/files/correspondence/gac-to-icann-28jun18-en.pdf</a> [PDF, 576 KB]<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.0pt">Barcelona Communiqué (25 October 2018): <a href="https://www.icann.org/en/system/files/correspondence/gac-to-icann-25oct18-en.pdf">
https://www.icann.org/en/system/files/correspondence/gac-to-icann-25oct18-en.pdf</a>
<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.0pt">The GNSO Council's review of the advice in the Barcelona Communiqué as presented in the 21 December 2018 letter to the Board:
<a href="https://www.icann.org/en/system/files/correspondence/drazek-et-al-to-icann-board-21dec18-en.pdf">
https://www.icann.org/en/system/files/correspondence/drazek-et-al-to-icann-board-21dec18-en.pdf</a>
<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.0pt">The GAC's clarification of Barcelona Communqiué Attach Language – Follow-up to Original Joint Statement by ALAC and GAC (Abu Dhabi, 2 November 2017):
<a href="https://www.icann.org/en/system/files/correspondence/ismail-to-chalaby-botterman-20dec18-en.pdf">
https://www.icann.org/en/system/files/correspondence/ismail-to-chalaby-botterman-20dec18-en.pdf</a>
<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.0pt">The ICANN Organization's memorandum providing clarification regarding the development and evolution of ICANN organization's procedure for the release of two-character labels at the second level and the standard framework of measures
for avoiding confusion with corresponding country codes: <a href="https://www.icann.org/en/system/files/files/implementation-memo-two-character-ascii-labels-22jan19-en.pdf">
https://www.icann.org/en/system/files/files/implementation-memo-two-character-ascii-labels-22jan19-en.pdf</a>
<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.0pt">The ICANN Organization's Historical Overview of Events Regarding Two-Character Labels at the Second Level in the New gTLD Namespace:
<a href="https://www.icann.org/en/system/files/files/historical-overview-two-character-ascii-labels-22jan19-en.pdf">
https://www.icann.org/en/system/files/files/historical-overview-two-character-ascii-labels-22jan19-en.pdf</a>
<o:p></o:p></span></li></ul>
<p>The adoption of the GAC advice as provided in the scorecard will have a positive impact on the community because it will assist with resolving the advice from the GAC concerning gTLDs and other matters. There are no foreseen fiscal impacts associated with
the adoption of this resolution. Approval of the resolution will not impact security, stability or resiliency issues relating to the DNS. This is an Organizational Administrative function that does not require public comment.<o:p></o:p></p>
<p class="MsoNormal"><b><i><span style="font-size:10.0pt;color:black">Marika Konings</span></i></b><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Email: <a href="mailto:marika.konings@icann.org"><span style="color:#0563C1">marika.konings@icann.org</span></a> </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black"> </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Follow the GNSO via Twitter @ICANN_GNSO</span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Find out more about the GNSO by taking our <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e="><span style="color:#0563C1">interactive
courses</span></a> and visiting the <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=tT-E2RoAucUb3pfL9zmlbRdq1sytaEf765KOEkBVCjk&e="><span style="color:#0563C1">GNSO
Newcomer pages</span></a>. </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>