<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:"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:"Noto Sans";
panose-1:2 11 5 2 4 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:24.0pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-GB;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">For your information: </span><a href="https://www.icann.org/en/blogs/details/icann-board-greenlights-implementation-of-registration-data-request-service-01-03-2023-en">https://www.icann.org/en/blogs/details/icann-board-greenlights-implementation-of-registration-data-request-service-01-03-2023-en</a><span lang="EN-US">
as well as the related Board resolution <a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en#section1.a">
https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en#section1.a</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Marika<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<h1 style="background:#FEFEFE"><span style="font-family:"Noto Sans",sans-serif;color:#333333">ICANN Board Greenlights Implementation of Registration Data Request Service<o:p></o:p></span></h1>
<p class="MsoNormal" style="background:#FEFEFE"><b><span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">1 March 2023<o:p></o:p></span></b></p>
<p class="MsoNormal" style="background:#FEFEFE"><span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">By <a href="https://www.icann.org/"><b><span style="color:#047BC1">Tripti Sinha</span></b></a><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center;background:#FEFEFE">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">
<hr size="0" width="100%" align="center">
</span></div>
<p style="background:#FEFEFE;box-sizing: inherit;margin:1.5rem;font-size:1rem;line-height:1.5rem;text-rendering: optimizelegibility">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">During a Special Meeting on 27 February 2023, the ICANN Board of Directors passed a <a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en#section1.a"><span style="color:#047BC1">resolution</span></a> directing
the ICANN organization (org) to develop and launch a new ticketing system to handle requests for access to nonpublic registration data related to generic top-level domains (gTLDs). The WHOIS Disclosure System, a proof of concept intended to gather usage and
demand data, streamlines the process for submitting and receiving requests for nonpublic gTLD registration data for ICANN-accredited registrars. These registrars would determine if the requestor has a legitimate need for this information from entities such
as law enforcement, government agencies, and intellectual property professionals.<o:p></o:p></span></p>
<p style="background:#FEFEFE;box-sizing: inherit;margin:1.5rem;font-size:1rem;line-height:1.5rem;text-rendering: optimizelegibility">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">This nonpublic data, formerly known as WHOIS information, encompasses personal data, such as a contact name, home or email address, and phone number. Once public and easily accessible,
this data is not necessarily published anymore due to personal data protection regulations and requires legitimate purposes for requesting and receiving it.<o:p></o:p></span></p>
<p style="background:#FEFEFE;box-sizing: inherit;margin:1.5rem;font-size:1rem;line-height:1.5rem;text-rendering: optimizelegibility">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">The system, which will be renamed during the development process, will connect requestors seeking nonpublic registration data with the relevant ICANN-accredited registrars for gTLD
domain names. The system will not deliver registration data, links, or instructions to access registration data to the requestors; all communication and data disclosure between the requestors and registrars will take place outside of the system. The registrars
are solely responsible for assessing the request and making the decision of whether to disclose the requested data in accordance with local laws.<o:p></o:p></span></p>
<p style="background:#FEFEFE;box-sizing: inherit;margin:1.5rem;font-size:1rem;line-height:1.5rem;text-rendering: optimizelegibility">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">The system was proposed in response to a Generic Names Supporting Organization (GNSO) Council request for ICANN org to implement a "proof of concept" system to gather usage and
demand data that would inform community discussions and Board consideration of the <a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phase-2-temp-spec-gtld-registration-data-2-31jul20-en.pdf"><span style="color:#047BC1">Phase
2 Recommendations</span></a> of the Expedited Policy Development Process (EPDP) relating to a System for Standardized Access/Disclosure. ICANN org will collect the relevant usage data for up to two years. To ensure that enough information is gathered, the
resolution contains a recommendation urging the GNSO Council to promote "comprehensive" or universal use of the service among ICANN-accredited registrars and potential requestors.<o:p></o:p></span></p>
<p style="background:#FEFEFE;box-sizing: inherit;margin:1.5rem;font-size:1rem;line-height:1.5rem;text-rendering: optimizelegibility">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">In taking this resolution, the ICANN Board reviewed the <a href="https://www.icann.org/en/system/files/files/whois-disclosure-system-design-paper-13sep22-en.pdf"><span style="color:#047BC1">WHOIS
Disclosure System Design Paper</span></a>, the EPDP Phase 2 Small Team's <a href="https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos-to-gnso-council-et-al-04apr22-en.pdf"><span style="color:#047BC1">4 April 2022 Preliminary Report
to the GNSO Council</span></a>, the <a href="https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos-to-gnso-council-07nov22-en.pdf"><span style="color:#047BC1">7 November 2022 addendum</span></a> to the EPDP Phase 2 Small Team's Preliminary
Report, the <a href="https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22-en.pdf"><span style="color:#047BC1">17 November 2022 letter</span></a> from the GNSO Council to the ICANN Board, and the recommendation from the Board Finance
Committee to allocate an envelope from the Supplemental Fund for Implementation of Community Recommendations for this work. The decision also considers ICANN's Bylaws, compliance with the law, the Board's fiduciary duties, and the costs associated with initial
implementation and subsequent operation of the system.<o:p></o:p></span></p>
<p style="background:#FEFEFE;box-sizing: inherit;margin:1.5rem;font-size:1rem;line-height:1.5rem;text-rendering: optimizelegibility">
<span style="font-size:12.0pt;font-family:"Noto Sans",sans-serif;color:#333333">ICANN org began a three-month project ramp-up period in December 2022; implementation is expected to take 11 months. The org anticipates working closely with the EPDP Phase 2 Small
Team that's advising on this process, as well as ICANN-accredited registrars, throughout development of the system.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>