<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:398137576;
mso-list-type:hybrid;
mso-list-template-ids:-1615716722 -1951614300 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:•;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.5in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
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;
margin-left:2.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
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;
margin-left:4.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">For your information. </span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><img width="625" height="48" style="width:6.5104in;height:.5in" id="Picture_x0020_2" src="cid:image001.jpg@01D3FCB8.47757B60" alt="cid:image001.jpg@01D3FC1D.ED5973B0"><o:p></o:p></p>
<p class="MsoNormal" align="right" style="text-align:right"> <o:p></o:p></p>
<p class="MsoNormal" align="right" style="text-align:right">4 June 2018<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Greetings,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The ICANN Global Domains Division (GDD) Services & Engagement team would like to highlight some recent, more notable, community-impacting activities and projects below. We are preparing for the
<a href="https://meetings.icann.org/en/panamacity62">ICANN62 Policy Forum</a> in Panama City, Panama and look forward to your participation.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:16.0pt">New & Noteworthy</span></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Temporary Specification for gTLD Registration Data</b><o:p></o:p></p>
<p class="MsoNormal">The General Data Protection Regulation (GDPR) was adopted by the European Union (EU) in April 2016 and took full effect on 25 May 2018. On 17 May 2018, ICANN published the
<a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en">Temporary Specification for gTLD Registration Data</a> (Temporary Specification). This Temporary Specification establishes temporary requirements to allow ICANN and gTLD registry
operators and registrars to continue to comply with existing ICANN contractual requirements and community-developed policies in light of the GDPR. The Temporary Specification applies to all of ICANN’s contracted parties and is now in effect as of 25 May 2018.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>GDPR and Temporary Specification Webinar </b><o:p></o:p></p>
<p class="MsoNormal">To offer further guidance and to learn how your organization may be affected by the Temporary Specification, we have scheduled a one-hour, interactive webinar on 6 June 2018. This will be a live webinar, held in English with live interpretation
in Arabic, Chinese, French, Russian, and Spanish, and we encourage you to email your questions ahead of time to
<a href="mailto:globalsupport@icann.org">globalsupport@icann.org</a> with “GDD Temp Spec Webinar” in the email’s subject line. A recording of the webinar will be posted as soon as possible on
<a href="http://icann.org">icann.org</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b>Webinar Details & How to Attend</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Date: 6 June 2018<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Time: 16:00 - 17:00 UTC (<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NSp+Roadmap+for+Registrars+Webinar&iso=20180613T14&p1=1440&ah=1">click here</a> to view time zone converter)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Join via Adobe Connect meeting <a href="https://participate.icann.org/tempspec06june2018">
here</a> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">View dial-in information <a href="https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=8021705257&num=1-605-475-5604">
here</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Participant Code: 802 170 5257<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Contracted Parties Encouraged to Prepare for RDAP</b><o:p></o:p></p>
<p class="MsoNormal">As indicated in Section 1 of <a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#appendixA">
Appendix A</a> of the <a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en">
Temporary Specification for gTLD Registration Data</a> (Temporary Specification), the ICANN organization intends to invoke the requirements in the registry and registrar agreements for implementation of the
<a href="https://www.icann.org/rdap">Registration Data Access Protocol</a> (RDAP) service. Currently, several contracted parties are participating in an RDAP
<a href="https://www.icann.org/news/announcement-2017-09-05-en">pilot program</a> to gain operational experience with RDAP and to define the appropriate operating profile(s) for the service. This pilot program is available to all community members. ICANN urges
all registries and registrars to begin preparing to operate an RDAP service as the technical development of the service may take several months. Please see the
<a href="https://www.icann.org/rdap">RDAP page</a> for more information. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Privacy Policy Notification to Contracted Parties</b><o:p></o:p></p>
<p class="MsoNormal">On Friday, 25 May 2018, the ICANN org updated its privacy policies and certain website terms of service to provide greater transparency, promote simplification, and align with recent changes in privacy laws applicable to ICANN org under
the GDPR. To learn more, please visit <a href="https://www.icann.org/privacy">https://www.icann.org/privacy</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>2018 GDD Industry Summit</b><o:p></o:p></p>
<p class="MsoNormal">The fourth annual <a href="https://www.icann.org/gddsummit">
Global Domains Division Industry Summit</a> was held in Richmond, British Columbia, Canada, from 14-17 May. Over 400 stakeholders attended from 32 countries. The primary purpose of the summit is to provide a forum for ICANN’s contracted parties to discuss issues
of mutual interest and importance, share best practices, and meet one-on-one with members of the ICANN org. This year, a multiple track format was added with one track dedicated to technical operations. The ICANN org is currently scouting an appropriate location
in the Asia-Pacific region for the 2019 summit. In 2020, the GDD Industry Summit will be held in Europe.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Domain Name Marketplace Indicators</b><o:p></o:p></p>
<p class="MsoNormal">ICANN org concluded its assessment of the draft V1.0 indicator schema, jointly developed with the project Advisory Panel, for all vendor proposals received. The project was awarded to
<a href="http://www.zooknic.com/">ZookNIC, Inc</a>. In April, the project team presented its proposed design approach and methodology to the Advisory Panel. The schema evaluation effort will conclude by the end of August 2018. Upon completion of the evaluation,
ICANN org intends to procure the external data sources necessary to finalize the V1.0 Indicators for publication prior to the end of the calendar year.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Final Proposed Draft Version 4.0 of the IDN Guidelines Now Published</b><o:p></o:p></p>
<p class="MsoNormal">The Internationalized Domain Name <a href="https://www.icann.org/resources/pages/implementation-guidelines-2012-02-25-en">
(IDN) Implementation Guidelines</a> relate to IDN registration policies and practices and are designed to minimize the risk of cybersquatting and consumer confusion. Once approved by the ICANN Board, these guidelines are contractually binding for most gTLD
registries and registrars offering IDN registrations. After multiple public consultations and review of current IDN Guidelines
<a href="https://www.icann.org/resources/pages/idn-guidelines-2011-09-02-en">version 3.0</a>, the
<a href="https://community.icann.org/display/IDN/IDN+Implementation+Guidelines">IDN Guidelines Working Group</a> has
<a href="https://www.icann.org/news/announcement-2018-05-10-en">published</a> the updated
<a href="https://www.icann.org/en/system/files/files/idn-guidelines-10may18-en.pdf">
Final Proposed Draft version 4.0</a> of the IDN Guidelines. This draft is pending approval from the ICANN Board of Directors. After approval, version 4.0 of the guidelines will become applicable to the relevant registries and registrars.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Contracted Parties Satisfaction Survey</b><o:p></o:p></p>
<p class="MsoNormal">In April 2018, the annual contracted parties satisfaction survey concluded. The objective of this survey was to understand and track feedback on the GDD’s work with contracted parties on an annual basis, based on the following dimensions:
integrity, dependability, competence, commitment, and satisfaction. The <a href="https://www.icann.org/resources/pages/metrics-gdd-2015-01-30-en">
published results</a> include a slide presentation with aggregated answers to each of the 12 survey questions and an executive summary.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Naming Services Portal Terms of Use</b><o:p></o:p></p>
<p class="MsoNormal">On 11 May 2018, changes to the Naming Services portal’s Terms of Use were deployed. Users who have not yet activated their accounts received an activation email. Please activate your account as soon as possible.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">For additional information regarding the features and functionality of the portal, please visit the
<a href="https://www.icann.org/resources/pages/registry-resources-2017-09-22-en">
Registry Resources</a> or <a href="https://www.icann.org/resources/pages/nsp-registrars-2018-03-26-en">
Naming Services portal for Registrars</a> pages on <a href="http://icann.org">icann.org</a>. These pages include webinar recordings, user guides, and additional resources. Please email
<a href="mailto:globalsupport@icann.org">globalsupport@icann.org</a> or contact your engagement manager with any questions.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ICANN to Publish Semi-Annual Report on WHOIS Accuracy</b><o:p></o:p></p>
<p class="MsoNormal">In mid-June, the ICANN org will publish the Phase 2 Cycle 6 WHOIS Accuracy Reporting System (ARS) Report. This report is a follow-up to previous ARS reports which have been published semi-annually since December 2015 and explores the syntax
and operability accuracy of WHOIS records in gTLDs in light of the requirements of the 2009 and 2013 Registrar Accreditation Agreements (RAAs). It also examines the leading types of nonconformance, trends, and comparisons of WHOIS accuracy across gTLD types,
ICANN regions, and RAA versions. Additional information about the project is available at
<a href="http://whois.icann.org/whoisars">whois.icann.org/whoisars</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ICANN Finance Department to Annually Publish Tax Residency Certificate</b><o:p></o:p></p>
<p class="MsoNormal">Effective this year and annually thereafter, the ICANN org will
<a href="https://www.icann.org/resources/pages/payments-2012-02-25-en">publish</a>: (1) the lCANN certification letter stating it is a tax resident of United States; and (2) Form 6166 - U.S. Tax Residency Certification for the relevant year. We expect the certificates
from the U.S. Internal Revenue Service will be published annually by ICANN org in the month of March. Tax residency forms for the years 2016, 2017 and 2018 are available on the
<a href="https://www.icann.org/resources/pages/payments-2012-02-25-en">ICANN Billing and Payments page</a>. If you have questions, please submit a general inquiry case via the Naming Service portal or email
<a href="mailto:globalsupport@icann.org">globalsupport@icann.org</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>The 2018 Contractual Compliance Quarter One Performance Report
</b><o:p></o:p></p>
<p class="MsoNormal">In March 2018, the ICANN org published a <a href="https://www.icann.org/resources/pages/compliance-reports-2018">
blog</a> on Enhancing Transparency in Contractual Compliance. As described in the
<a href="https://www.icann.org/resources/pages/compliance-reports-2018">report and blog</a>, Contractual Compliance completed its work on
<a href="https://features.icann.org/compliance">enhanced metrics and performance reports</a>. Contractual Compliance team members will be attending the ICANN62 Policy Forum and available for a limited number of one-on-one sessions with contracted parties, which
can be requested by emailing <a href="mailto:compliance@icann.org">compliance@icann.org</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:16.0pt">Policy Implementation Updates</span></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Protection of IGO and INGO Identifiers for All gTLDs</b><o:p></o:p></p>
<p class="MsoNormal">On 16 January 2018, the Implementation of the Protection of IGO and INGO Identifiers for all gTLDs Policy was
<a href="https://www.icann.org/resources/pages/igo-ingo-protection-policy-2018-01-16-en">
published</a>. Contracted parties have until 1 August 2018 to complete implementation of the new requirements for specified names of IGOs, the International Olympic Committee (IOC), and the Red Cross/Red Crescent Movement (RCRC). For INGOs, the implementation
period will be 12 months from the release of the INGO Claims Systems Specification, which is currently under development.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Thick WHOIS Transition Consensus Policy </b><o:p></o:p></p>
<p class="MsoNormal">On 13 May 2018, the ICANN Board passed a <a href="https://www.icann.org/resources/board-material/resolutions-2018-05-13-en#1.e">
Resolution</a> to defer contractual compliance enforcement of the Thick WHOIS transition policy in consideration of the European Union's General Data Protection Regulation (GDPR). ICANN Contractual Compliance will defer enforcing the following milestones until
the dates listed below:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">•<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>30 November 2018: The registry operator must begin accepting Thick WHOIS data from registrars for existing registrations in .COM, .NET and .JOBS.<o:p></o:p></p>
<p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">•<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>By 30 April 2019: All registrars must send Thick WHOIS data to the registry operator for all new registrations in .COM, .NET and .JOBS.<o:p></o:p></p>
<p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">•<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>By 31 January 2020: All registrars are required to complete the transition to Thick WHOIS data for all registrations in .COM, .NET and .JOBS.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">For more information, please refer to the published Thick WHOIS Transition Policy available
<a href="https://www.icann.org/resources/pages/thick-whois-transition-policy-2017-02-01-en">
here</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Privacy/Proxy Service Provider Accreditation Program</b><o:p></o:p></p>
<p class="MsoNormal">ICANN org continues to work with the volunteer Implementation Review Team (IRT) on implementing the generic names supporting organization’s (GNSO) recommendations for a
<a href="https://www.icann.org/resources/pages/ppsai-2016-08-18-en">proxy/privacy service provider accreditation</a> program. The ICANN org received a
<a href="https://www.icann.org/en/system/files/correspondence/bunton-to-atallah-04may18-en.pdf">
request from the RrSG on 4 May 2018</a> to pause the IRT’s work, and a <a href="https://www.icann.org/en/system/files/correspondence/marks-metalitz-to-atallah-namazi-10may18-en.pdf">
communication opposing this from the Coalition for Online Accountability</a> on 10 May 2018. These requests are currently under consideration. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:16.0pt">Registrars</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:16.0pt"> </span></b><o:p></o:p></p>
<p class="MsoNormal"><b>Naming Services Portal – Registrar</b><o:p></o:p></p>
<p class="MsoNormal">ICANN recently launched the Naming Services portal for Registrars, an application built to streamline the way registrars conduct business with the ICANN org. This recent launch is a step towards in making the Naming Services portal the
primary system of record and replacing legacy systems. As part of this release, all registrar primary contacts now have access to the portal with the ability to view the compliance tickets for the relevant IANA IDs. The ICANN org is continuing to work with
a registrar portal planning group to gather input on the future feature enhancements to the portal.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Webinar Announcement: Naming Services Portal Roadmap </b>
<o:p></o:p></p>
<p class="MsoNormal">ICANN org will hold a webinar scheduled on 13 June 2018 to discuss the Naming Service portal for registrars, its current capabilities, and the roadmap for future releases. Participants have an opportunity to provide feedback and ask questions
directly from the product team. A recording of the webinar will be made available following the session.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b>Webinar Details & How to Attend</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Date: 13 June 2018<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Time: 14:00 - 15:00 UTC (<a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=NSp+Roadmap+for+Registrars+Webinar&iso=20180613T14&p1=1440&ah=1">click here</a> to view time zone converter)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://participate.icann.org/nspwebinar/">Join Via Adobe Connect</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=2897077927&num=1-605-475-5606">Via Dial-In Information</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Participant Code: 289 707 7927 <o:p>
</o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>2013 Registrar Accreditation Agreement (RAA) Renewal</b><o:p></o:p></p>
<p class="MsoNormal">The initial set of early adopters that executed the 2013 RAA are nearing the auto-renewal process. The steps for the RAA auto-renewal process are detailed
<a href="https://www.icann.org/resources/pages/renewing-2013-07-08-en">here</a>. Registrars who meet the criteria will have their agreements auto-renewed for a new five-year term of accreditation.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Additional ICANN-designated Registrar Data Escrow Agent</b><o:p></o:p></p>
<p class="MsoNormal">ICANN org <a href="https://www.icann.org/news/announcement-3-2018-05-15-en">
announced</a> DENIC eG as an additional ICANN-designated Registrar Data Escrow Agent. Registrars wishing to change their escrow agent should follow the
<a href="https://www.icann.org/resources/pages/registrar-data-escrow-agent-change-2018-05-14-en">
Registrar Data Escrow Agent Change</a> process.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:16.0pt">Registries</span></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>New Registry Resources Available on <a href="http://icann.org">
icann.org</a></b><o:p></o:p></p>
<p class="MsoNormal">One of the Registry Services & Engagement team’s goals in the coming year is to review and update the
<a href="https://www.icann.org/resources/pages/registry-resources-2017-09-22-en">
registry resources</a> available on <a href="http://icann.org">icann.org</a>. We recently published the
<a href="https://www.icann.org/en/system/files/files/gdd-ops-handbook-registry-operators-01jun18-en.pdf">
GDD Handbook</a>, and the <a href="https://www.icann.org/en/system/files/files/registry-operator-billing-faqs-30may18-en.pdf">
Registry Billing Frequently Asked Questions</a>. If you have feedback or suggestions regarding registry resources, please submit a general inquiry via the Naming Services portal or email
<a href="mailto:globalsupport@icann.org">globalsupport@icann.org</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Procedure for Community gTLD Change Requests</b><o:p></o:p></p>
<p class="MsoNormal">The ICANN org and the Community gTLD Change Request Working Group discussed updates to the draft procedure based on the comments received during
<a href="https://www.icann.org/public-comments/community-gtld-change-procedure-2018-02-14-en">
Public Comment</a> and finalized an updated version available <a href="https://www.icann.org/resources/pages/community-gtld-change-requests-procedure-2018-06-01-en">
here</a>. The ICANN org is preparing to offer this service for community gTLD registry operators with an expected launch date in July 2018.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Registry Service and Evaluation Policy (RSEP) Process Improvements </b><o:p></o:p></p>
<p class="MsoNormal">Representatives from the Registries Stakeholder Group (RySG) and ICANN org are reviewing the RSEP submission and review process. The objective is to find ways to improve timelines from the initial RSEP request through ICANN approval while
providing more clarity to registries in each stage of the process. Following a review of proposed updates to the operational process at the GDD Industry Summit in Richmond, British Columbia, the RySG will provide feedback to staff, and this will be discussed
in more detail at ICANN62.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We hope this information provides you with additional insight and transparency into our ongoing activities and look forward to your feedback.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
<p class="MsoNormal">Cyrus Namazi<o:p></o:p></p>
<p class="MsoNormal">Vice President, Domain Name Services & Industry Engagement<o:p></o:p></p>
<p class="MsoNormal">ICANN Global Domains Division<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><img border="0" width="935" height="72" style="width:9.7395in;height:.75in" id="image001.jpg_x0040_01D3FC23.2C1C3F60" src="cid:image001.jpg@01D3FCB8.47757B60" alt="cid:image001.jpg@01D3FC23.2C1C3F60"><o:p></o:p></span></p>
</div>
</blockquote>
</div>
</body>
</html>