<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:"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.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.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: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;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Alex,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are planning to release the update by May.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">-- <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">Francisco</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in">On 2/27/19, 11:14 PM, "Alexander Mayrhofer" <<a href="mailto:alexander.mayrhofer@nic.at">alexander.mayrhofer@nic.at</a>> wrote:<span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D">Francisco,</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D">can you give us a timeline for the potential extension of the “Registrar ID” registry at IANA (</span><a href="https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml"><span style="font-size:11.0pt">https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml</span></a><span style="font-size:11.0pt;color:#1F497D">)?
 – I understand that the RDAP base URL is to be added there, so that registries don’t need to collect that information from registrars individually. Since we’d like to test that rather soon, it would be appreciated if that extension happened rather sooner than
 later.</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D">Best,</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D">Alex</span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span lang="DE" style="font-size:11.0pt">Von:</span></b><span lang="DE" style="font-size:11.0pt"> gtld-tech <gtld-tech-bounces@icann.org>
<b>Im Auftrag von </b>Francisco Arias<br>
<b>Gesendet:</b> Donnerstag, 28. Februar 2019 00:34<br>
<b>An:</b> gtld-tech@icann.org<br>
<b>Betreff:</b> [gtld-tech] FYI: RDAP service in the gTLD space</span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<p class="MsoNormal" style="margin-left:.5in">Today, ICANN org issued a notification to gTLD registries and registrars of the requirement to implement an RDAP service by 26 August 2019.</p>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://www.icann.org/resources/pages/rdap-implementers-resources-2018-08-31-en">https://www.icann.org/resources/pages/rdap-implementers-resources-2018-08-31-en</a></p>
<p class="MsoNormal" style="margin-left:.5in"> </p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">-- </span></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Francisco</span></p>
</div>
</div>
</div>
</body>
</html>