<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Thanks Dennis, <br>
    </p>
    <p>Theo <br>
    </p>
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 12-9-2016 21:54, Dennis Chang wrote:<br>
    </div>
    <blockquote
      cite="mid:1A27E01F-FE13-4164-9DF2-18953060D18B@icann.org"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <meta name="Title" content="">
      <meta name="Keywords" content="">
      <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:Arial;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:"맑은 고딕";}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:PMingLiU;
        panose-1:2 2 5 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
h2
        {mso-style-priority:9;
        mso-style-link:"Heading 2 Char";
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:18.0pt;
        font-family:"Times New Roman";
        font-weight:bold;}
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
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman";}
span.Heading2Char
        {mso-style-name:"Heading 2 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 2";
        font-weight:bold;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:Calibri;
        color:#1F497D;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:Calibri;
        color:windowtext;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:Calibri;
        color:windowtext;}
span.msoIns
        {mso-style-type:export-only;
        mso-style-name:"";
        text-decoration:underline;
        color:teal;}
.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:1667977863;
        mso-list-template-ids:2080792520;}
@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:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style>
      <div class="WordSection1">
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:Calibri">That’s right
            Theo.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:Calibri">We have another
            meeting already scheduled on the following week
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:Calibri">and the agenda
            for that meeting will be set at the end of tomorrow’s
            meeting.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
        <div>
          <div>
            <p class="MsoNormal"><span
                style="font-size:10.5pt;font-family:Calibri;color:black">Thanks<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><span
            style="font-size:10.5pt;font-family:Calibri;color:black">Dennis
            Chang</span><span
            style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
        <div style="border:none;border-top:solid #B5C4DF
          1.0pt;padding:3.0pt 0in 0in 0in">
          <p class="MsoNormal"><b><span
                style="font-family:Calibri;color:black">From: </span>
            </b><span style="font-family:Calibri;color:black">theo
              geurts <a class="moz-txt-link-rfc2396E" href="mailto:gtheo@xs4all.nl">&lt;gtheo@xs4all.nl&gt;</a><br>
              <b>Date: </b>Monday, September 12, 2016 at 12:48 PM<br>
              <b>To: </b>Dennis Chang <a class="moz-txt-link-rfc2396E" href="mailto:dennis.chang@icann.org">&lt;dennis.chang@icann.org&gt;</a>,
              "Metalitz, Steven" <a class="moz-txt-link-rfc2396E" href="mailto:met@msk.com">&lt;met@msk.com&gt;</a><br>
              <b>Cc: </b><a class="moz-txt-link-rfc2396E" href="mailto:gnso-impl-thickwhois-rt@icann.org">"gnso-impl-thickwhois-rt@icann.org"</a>
              <a class="moz-txt-link-rfc2396E" href="mailto:gnso-impl-thickwhois-rt@icann.org">&lt;gnso-impl-thickwhois-rt@icann.org&gt;</a><br>
              <b>Subject: </b>Re: [Gnso-impl-thickwhois-rt] [for iRT
              review] Draft Thick Whois Transition Policy for .COM,
              .NET, and .JOBS<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
        <div>
          <div>
            <p>Thanks Dennis, <o:p></o:p></p>
            <p>Regarding the agenda items, if we do not get through all
              of them they will be automatically moved to the next call
              right?<o:p></o:p></p>
            <p>Best, <o:p></o:p></p>
            <p>Theo <o:p></o:p></p>
            <p><o:p> </o:p></p>
            <p class="MsoNormal"><o:p> </o:p></p>
            <div>
              <p class="MsoNormal">On 12-9-2016 21:39, Dennis Chang
                wrote:<o:p></o:p></p>
            </div>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri">Hi Steve,</span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri">The
                  agenda and the latest documents were distributed last
                  week as attached and the draft letter is on the
                  agenda.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri">The IRT
                  agenda can be also be found on the IRT wiki:
                  <a moz-do-not-send="true"
href="https://community.icann.org/display/TWCPI/IRT+Meetings#IRTMeetings-13September2016">https://community.icann.org/display/TWCPI/IRT+Meetings#IRTMeetings-13September2016</a></span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri">Provided
                  below for your convenience.</span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri">I am
                  assuming all IRT members have access to the IRT wiki
                  page.  If not, please let me know.</span><o:p></o:p></p>
              <p class="MsoNormal"
                style="margin-top:22.5pt;background:white"><span
                  style="font-size:15.0pt;font-family:Arial;color:#333333">13
                  September 2016</span><o:p></o:p></p>
              <div class="MsoNormal" style="text-align:center"
                align="center">
                <hr style="color:#333333" align="center"
                  noshade="noshade" size="2" width="100%">
              </div>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level1 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Agenda:</span><o:p></o:p></p>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level2 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Transition
                  from thin to thick</span><o:p></o:p></p>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level3 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Draft
                  Consensus Policy document review - continue from
                  section 2.9</span><o:p></o:p></p>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level3 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Public
                  Comment readiness</span><o:p></o:p></p>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level2 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Whois
                  Conflict Procedure (if time permits)</span><o:p></o:p></p>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level2 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Draft
                  memo to GNSO Council regarding Privacy (if time
                  permits)</span><o:p></o:p></p>
              <p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;text-indent:-.25in;mso-list:l0
                level2 lfo2;background:white">
                <!--[if !supportLists]--><span
                  style="font-size:10.0pt;font-family:Symbol"><span
                    style="mso-list:Ignore">·<span style="font:7.0pt
                      &quot;Times New Roman&quot;">        
                    </span></span></span><!--[endif]--><span
                  style="font-size:10.5pt;font-family:Arial;color:#333333">Next
                  Steps</span><o:p></o:p></p>
              <div>
                <div>
                  <p class="MsoNormal"><span
                      style="font-size:10.5pt;font-family:Calibri;color:black">Thanks</span><o:p></o:p></p>
                </div>
              </div>
              <p class="MsoNormal"><span
                  style="font-size:10.5pt;font-family:Calibri;color:black">Dennis
                  Chang</span><o:p></o:p></p>
              <p class="MsoNormal"><span
                  style="font-size:11.0pt;font-family:Calibri"> </span><o:p></o:p></p>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"><b><span
                      style="font-family:Calibri;color:black">From: </span>
                  </b><span style="font-family:Calibri;color:black"><a
                      moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">&lt;gnso-impl-thickwhois-rt-bounces@icann.org&gt;</a>
                    on behalf of "Metalitz, Steven"
                    <a moz-do-not-send="true" href="mailto:met@msk.com">&lt;met@msk.com&gt;</a><br>
                    <b>Date: </b>Monday, September 12, 2016 at 11:32 AM<br>
                    <b>To: </b>'gtheo' <a moz-do-not-send="true"
                      href="mailto:gtheo@xs4all.nl">&lt;gtheo@xs4all.nl&gt;</a><br>
                    <b>Cc: </b><a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">"gnso-impl-thickwhois-rt@icann.org"</a>
                    <a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">&lt;gnso-impl-thickwhois-rt@icann.org&gt;</a><br>
                    <b>Subject: </b>Re: [Gnso-impl-thickwhois-rt] [for
                    iRT review] Draft Thick Whois Transition Policy for
                    .COM, .NET, and .JOBS</span><o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"> <o:p></o:p></p>
              </div>
              <div>
                <div>
                  <p class="MsoNormal"><span
                      style="font-size:11.0pt;font-family:Calibri;color:#1F497D">I
                      have not yet seen any agenda for tomorrow’s call
                      but assuming that it includes a discussion of the
                      Verisign draft letter to GNSO council, it would be
                      great to have Verisign’s responses to the
                      questions about it that I posed two weeks ago. 
                      See below.  </span>
                    <o:p></o:p></p>
                  <p class="MsoNormal"><span
                      style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
                  <div>
                    <p class="MsoNormal"><b><span
                          style="font-size:11.0pt;font-family:Calibri;color:#88162E"><img
                            id="Picture_x005f_x005f_x005f_x0020_1"
                            src="cid:part7.2781BD37.3B232DC5@xs4all.nl"
                            alt="age001" height="41" border="0"
                            width="124"></span></b><o:p></o:p></p>
                    <p class="MsoNormal"><b><span
                          style="font-size:11.0pt;font-family:Calibri;color:#88162E">Steven
                          J. Metalitz
                        </span></b><span
                        style="font-size:11.0pt;font-family:Calibri;color:black">|<b>
                        </b>
                      </span><b><span
                          style="font-size:11.0pt;font-family:Calibri;color:#88162E">Partner,
                          through his professional corporation</span></b><o:p></o:p></p>
                    <p class="MsoNormal"><span
                        style="font-size:10.0pt;font-family:Calibri;color:black">T:
                        202.355.7902 |
                        <a moz-do-not-send="true"
                          href="mailto:met@msk.com"><span
                            style="color:black">met@msk.com</span></a></span><o:p></o:p></p>
                    <p class="MsoNormal"><b><span
                          style="font-size:10.0pt;font-family:Calibri;color:#88162E">Mitchell
                          Silberberg &amp; Knupp</span></b><span
                        style="font-size:11.0pt;font-family:Calibri;color:#1F497D">
                      </span><b><span
                          style="font-size:8.0pt;font-family:Calibri;color:#88162E">LLP</span></b><span
style="font-size:10.0pt;font-family:Calibri;color:#84162E">
                      </span><span
                        style="font-size:10.0pt;font-family:Calibri;color:black">|</span><span
style="font-size:10.0pt;font-family:Calibri;color:#84162E">
                        <b><a moz-do-not-send="true"
                            href="http://www.msk.com/"><span
                              style="color:#84162E">www.msk.com</span></a></b></span><o:p></o:p></p>
                    <p class="MsoNormal"><span
                        style="font-size:10.0pt;font-family:Calibri;color:black">1818
                        N Street NW, 8th Floor, Washington, DC 20036</span><o:p></o:p></p>
                    <p class="MsoNormal"><span
                        style="font-size:10.0pt;font-family:Calibri;color:black"> </span><o:p></o:p></p>
                    <p class="MsoNormal" style="text-autospace:none"><b><u><span
style="font-size:8.0pt;font-family:Calibri;color:gray">THE INFORMATION
                            CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED
                            ONLY FOR THE PERSONAL AND CONFIDENTIAL USE
                            OF THE DESIGNATED RECIPIENTS.</span></u></b><b><span
style="font-size:8.0pt;font-family:Calibri;color:gray"> THIS MESSAGE MAY
                          BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS
                          SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE
                          READER OF THIS MESSAGE IS NOT AN INTENDED
                          RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY
                          REVIEW, USE, DISSEMINATION, FORWARDING OR
                          COPYING OF THIS MESSAGE IS STRICTLY
                          PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY
                          REPLY E-MAIL OR TELEPHONE, AND DELETE THE
                          ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR
                          SYSTEM. THANK YOU.</span></b><o:p></o:p></p>
                  </div>
                  <p class="MsoNormal"><span
                      style="font-size:11.0pt;font-family:Calibri;color:#1F497D"> </span><o:p></o:p></p>
                  <p class="MsoNormal"><br>
                    Metalitz, Steven schreef op 2016-09-08 05:25 PM:<br>
                    &gt; Theo’s ruminations lead me to repeat the
                    questions I posed to Marc<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; last week about his draft memo:<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; (1) The first two developments to which
                    you cite are the<br>
                    &gt; invalidation of the US-EU Safe Harbor Program
                    and the adoption of the<br>
                    &gt; EU-US Privacy Shield framework to replace it.
                    My impression is that<br>
                    &gt; US registries generally did not rely upon the
                    Safe Harbor in<br>
                    &gt; processing thick Whois data (e.g., receiving
                    Whois data containing<br>
                    &gt; personally identifiable information from
                    European registrars and<br>
                    &gt; making it available through registry Whois),
                    and so would not have<br>
                    &gt; been directly impacted by its invalidation. Is
                    my impression wrong?<br>
                    &gt; If I am correct then what is the relevance of
                    either the Safe Harbor<br>
                    &gt; or the Privacy Shield in this context?<br>
                    &gt; <br>
                    &gt; (2) The last paragraph refers to data
                    localization laws apart from<br>
                    &gt; EU privacy/data protection laws. Can you be
                    more specific? I note<br>
                    &gt; that the Russian law was referenced in
                    footnotes 2 and 10 of the legal<br>
                    &gt; review provided to the IRT in June 2015, are
                    there other issues not<br>
                    &gt; covered by that analysis?<br>
                    &gt; <br>
                    &gt; (3) If the IRT were to send this letter, the
                    GNSO council might<br>
                    &gt; well ask what (if anything) we are asking them
                    to do. How would you<br>
                    &gt; respond?<br>
                    &gt; <br>
                    &gt; In particular, If I understand Theo correctly,
                    his answer to #3 would<br>
                    &gt; be “please tear up the consensus policy
                    recommended by the Working<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Group, adopted by the GNSO Council, and
                    approved by the ICANN board,<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; it is obsolete, and let’s not waste
                    [further] time implementing<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; it.” Is that reading correct, and do
                    others in the IRT support<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; that?<span style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; STEVEN J. METALITZ | PARTNER, THROUGH
                    HIS PROFESSIONAL CORPORATION<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; T: 202.355.7902 | <a
                      moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a><br>
                    &gt; <br>
                    &gt; MITCHELL SILBERBERG &amp; KNUPP LLP | <a
                      moz-do-not-send="true" href="http://WWW.MSK.COM">WWW.MSK.COM</a>
                    [3]<br>
                    &gt; <br>
                    &gt; 1818 N Street NW, 8th Floor, Washington, DC
                    20036<br>
                    &gt; <br>
                    &gt; THE INFORMATION CONTAINED IN THIS E-MAIL
                    MESSAGE IS INTENDED ONLY FOR<br>
                    &gt; THE PERSONAL AND CONFIDENTIAL USE OF THE
                    DESIGNATED RECIPIENTS. THIS<br>
                    &gt; MESSAGE MAY BE AN ATTORNEY-CLIENT
                    COMMUNICATION, AND AS SUCH IS<br>
                    &gt; PRIVILEGED AND CONFIDENTIAL. IF THE READER OF
                    THIS MESSAGE IS NOT AN<br>
                    &gt; INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED
                    THAT ANY REVIEW, USE,<br>
                    &gt; DISSEMINATION, FORWARDING OR COPYING OF THIS
                    MESSAGE IS STRICTLY<br>
                    &gt; PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY
                    REPLY E-MAIL OR TELEPHONE,<br>
                    &gt; AND DELETE THE ORIGINAL MESSAGE AND ALL
                    ATTACHMENTS FROM YOUR SYSTEM.<br>
                    &gt; THANK YOU.<br>
                    &gt; <br>
                    &gt; FROM: gtheo [<a moz-do-not-send="true"
                      href="mailto:gtheo@xs4all.nl">mailto:gtheo@xs4all.nl</a>]<br>
                    &gt; SENT: Thursday, September 08, 2016 6:57 AM<br>
                    &gt; TO: Marika Konings; Metalitz, Steven; 'Volker
                    Greimann'<br>
                    &gt; CC: <a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt; SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for iRT
                    review] Draft Thick<br>
                    &gt; Whois Transition Policy for .COM, .NET, and
                    .JOBS<br>
                    &gt; <br>
                    &gt; Interesting review. After reading it I agree
                    with Volker here.<br>
                    &gt; <br>
                    &gt; Few things that stood out.<br>
                    &gt; <br>
                    &gt; It seems the focus was put on the 95/46/EC
                    Directive (makes sense) but<br>
                    &gt; Safe Harbor was not included in. I am not sure
                    if that was intended? I<br>
                    &gt; would not be surprised that anyone ever thought
                    that it would be a<br>
                    &gt; possibility that it would be invalidated, and
                    what the consequences<br>
                    &gt; are.<br>
                    &gt; <br>
                    &gt; Anyways, we just need a good procedure for this
                    IRT. The legal review<br>
                    &gt; does not address the current impediment, so
                    that is not up to us.<br>
                    &gt; <br>
                    &gt; What is up to us, maybe, are the benefits
                    mentioned in the legal<br>
                    &gt; review (page5)?<br>
                    &gt; <br>
                    &gt; Let me list them:<br>
                    &gt; 1. A thick Whois model offers attractive
                    archival and restoration<br>
                    &gt; properties. If a registrar were to go out of
                    business or experience<br>
                    &gt; long-term technical failures rendering<br>
                    &gt; them unable to provide service, registries
                    maintaining thick Whois<br>
                    &gt; have all the registrant information at hand and
                    could transfer the<br>
                    &gt; registrations to a different (or temporary)
                    registrar so that<br>
                    &gt; registrants could continue to manage their
                    domain names.<br>
                    &gt; <br>
                    &gt; 2. A thick Whois model reduces the degree of
                    variability in display<br>
                    &gt; formats.<br>
                    &gt; <br>
                    &gt; 3. Establishing requirements such as collecting
                    uniform sets of<br>
                    &gt; data, and display standards, improves
                    consistency across all gTLDs at<br>
                    &gt; all levels and result in better access to Whois
                    data for all users of<br>
                    &gt; Whois databases (e.g. law enforcement,
                    Intellectual Property holders,<br>
                    &gt; etc).<br>
                    &gt; <br>
                    &gt; 4. The uptime of the registry with respect to
                    Whois data has<br>
                    &gt; typically been found to be better (at least
                    marginally) than the<br>
                    &gt; registrar.<br>
                    &gt; <br>
                    &gt; I am not sure about the rest of you, but this
                    re-enforces the point<br>
                    &gt; that this migration has been in the freezer for
                    too long.<br>
                    &gt; <br>
                    &gt; Point 1, that's why we have escrow obligations.
                    The reasoning in<br>
                    &gt; point 1 is not sustainable for the future I am
                    afraid.<br>
                    &gt; Point 2 and 3, This has been addressed by the
                    RAA 2013 and the AWIP<br>
                    &gt; policy released in 2015.<br>
                    &gt; Point 4, I suspect with RDAP this problem will
                    also be solved.<br>
                    &gt; Beside the RAA 2013 also addresses this with an
                    SLA.<br>
                    &gt; <br>
                    &gt; One could almost argue there are no benefits.
                    Not sure if you guys<br>
                    &gt; want to circle back on this one and include
                    this in a side note for<br>
                    &gt; the comment period.<br>
                    &gt; <br>
                    &gt; Also, interesting to read but, out of scope for
                    this IRT (I think) is<br>
                    &gt; the RDAP solution (page 12 of the legal
                    review)? It could be me, but<br>
                    &gt; it almost looks like if there was a quick
                    procedure and workable<br>
                    &gt; procedure then the technical issue would be
                    solved also, and it would<br>
                    &gt; solve our impediment.<br>
                    &gt; <br>
                    &gt; Thank you for making it this far.<br>
                    &gt; <br>
                    &gt; Theo<br>
                    &gt; <br>
                    &gt; theo geurts schreef op 2016-09-07 10:22 PM:<br>
                    &gt; <br>
                    &gt;&gt; Thanks, Marika,<br>
                    &gt;&gt; <br>
                    &gt;&gt; I'll give that one a read tomorrow. Though
                    I think Volker is right.<br>
                    &gt;&gt; Seems we are operating under old marching
                    orders, Steve already<br>
                    &gt;&gt; warned<br>
                    &gt;&gt; us that this thing has taken way too long.
                    The draft Verisign<br>
                    &gt;&gt; prepared<br>
                    &gt;&gt; does actually highlight the current
                    situation. And to be fair? How<br>
                    &gt;&gt; many people would have thought that Safe
                    Harbor would have been<br>
                    &gt;&gt; invalidated? Not me for sure. But I also
                    did not predict the brexit<br>
                    &gt;&gt; or<br>
                    &gt;&gt; Trump running for president.<br>
                    &gt;&gt; <br>
                    &gt;&gt; In addition to this, I think we are in
                    agreement here. It is not up<br>
                    &gt;&gt; to<br>
                    &gt;&gt; this IRT. We can only signal the GNSO that
                    most likely we have a<br>
                    &gt;&gt; few<br>
                    &gt;&gt; impediments.<br>
                    &gt;&gt; <br>
                    &gt;&gt; Best regards,<br>
                    &gt;&gt; <br>
                    &gt;&gt; Theo<br>
                    &gt;&gt; <br>
                    &gt;&gt; On 7-9-2016 16:53, Marika Konings wrote:<br>
                    &gt;&gt; <br>
                    &gt;&gt; And it can be found here:<br>
                    &gt;&gt; <br>
                    &gt;&gt; <br>
                    &gt; <a moz-do-not-send="true"
href="https://community.icann.org/download/attachments/52889541/ICANN%20Memorandum%20to%20the%20IRT%20-%20Thin%20to%20Thick%20WHOIS%20Transition_Final_2015-06-08.pdf?version=1&amp;modificationDate=1434138098000&amp;api=v2">https://community.icann.org/download/attachments/52889541/ICANN%20Memorandum%20to%20the%20IRT%20-%20Thin%20to%20Thick%20WHOIS%20Transition_Final_2015-06-08.pdf?version=1&amp;modificationDate=1434138098000&amp;api=v2</a>.<br>
                    &gt;&gt; <br>
                    &gt;&gt; <br>
                    &gt;&gt; Best regards,<br>
                    &gt;&gt; <br>
                    &gt;&gt; Marika<br>
                    &gt;&gt; <br>
                    &gt;&gt; MARIKA KONINGS<br>
                    &gt;&gt; <br>
                    &gt;&gt; Senior Policy Director &amp; Team Leader
                    for the GNSO, Internet<br>
                    &gt;&gt; Corporation for Assigned Names and Numbers
                    (ICANN)<br>
                    &gt;&gt; <br>
                    &gt;&gt; Email: <a moz-do-not-send="true"
                      href="mailto:marika.konings@icann.org">marika.konings@icann.org</a><br>
                    &gt;&gt; <br>
                    &gt;&gt; _ _<br>
                    &gt;&gt; <br>
                    &gt;&gt; _Follow the GNSO via Twitter @ICANN_GNSO_<br>
                    &gt;&gt; <br>
                    &gt;&gt; _Find out more about the GNSO by taking our
                    interactive courses [10<br>
                    &gt;&gt; [1]]<br>
                    &gt;&gt; and visiting the GNSO Newcomer pages [11]._<br>
                    &gt;&gt; <br>
                    &gt;&gt; FROM: &lt;<a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>&gt;
                    on behalf of<br>
                    &gt;&gt; "Metalitz, Steven" &lt;<a
                      moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a>&gt;<br>
                    &gt;&gt; DATE: Wednesday 7 September 2016 at 08:44<br>
                    &gt;&gt; TO: 'Volker Greimann' &lt;<a
                      moz-do-not-send="true"
                      href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>&gt;,
                    gtheo<br>
                    &gt;&gt; &lt;<a moz-do-not-send="true"
                      href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>&gt;<br>
                    &gt;&gt; CC: "<a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a>"<br>
                    &gt;&gt; &lt;<a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a>&gt;<br>
                    &gt;&gt; SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for
                    iRT review] Draft Thick<br>
                    &gt;&gt; Whois Transition Policy for .COM, .NET, and
                    .JOBS<br>
                    &gt;&gt; <br>
                    &gt;&gt; That legal review was undertaken more than
                    a year ago.<br>
                    &gt;&gt; <br>
                    &gt;&gt; STEVEN J. METALITZ | PARTNER, THROUGH HIS
                    PROFESSIONAL CORPORATION<br>
                    &gt;&gt; <br>
                    &gt;&gt; T: 202.355.7902 | <a
                      moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a><br>
                    &gt;&gt; <br>
                    &gt;&gt; MITCHELL SILBERBERG &amp; KNUPP LLP | <a
                      moz-do-not-send="true" href="http://WWW.MSK.COM">WWW.MSK.COM</a>
                    [2] [1 [3]]<br>
                    &gt;&gt; <br>
                    &gt;&gt; 1818 N Street NW, 8th Floor, Washington, DC
                    20036<br>
                    &gt;&gt; <br>
                    &gt;&gt; THE INFORMATION CONTAINED IN THIS E-MAIL
                    MESSAGE IS INTENDED ONLY<br>
                    &gt;&gt; FOR THE PERSONAL AND CONFIDENTIAL USE OF
                    THE DESIGNATED RECIPIENTS.<br>
                    &gt;&gt; THIS MESSAGE MAY BE AN ATTORNEY-CLIENT
                    COMMUNICATION, AND AS SUCH IS<br>
                    &gt;&gt; PRIVILEGED AND CONFIDENTIAL. IF THE READER
                    OF THIS MESSAGE IS NOT AN<br>
                    &gt;&gt; INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED
                    THAT ANY REVIEW, USE,<br>
                    &gt;&gt; DISSEMINATION, FORWARDING OR COPYING OF
                    THIS MESSAGE IS STRICTLY<br>
                    &gt;&gt; PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY
                    REPLY E-MAIL OR<br>
                    &gt;&gt; TELEPHONE, AND DELETE THE ORIGINAL MESSAGE
                    AND ALL ATTACHMENTS FROM<br>
                    &gt;&gt; YOUR SYSTEM. THANK YOU.<br>
                    &gt;&gt; <br>
                    &gt;&gt; FROM: Volker Greimann [<a
                      moz-do-not-send="true"
                      href="mailto:vgreimann@key-systems.net">mailto:vgreimann@key-systems.net</a>]<br>
                    &gt;&gt; SENT: Wednesday, September 07, 2016 10:44
                    AM<br>
                    &gt;&gt; TO: Metalitz, Steven; gtheo<br>
                    &gt;&gt; CC: <a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt;&gt; SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for
                    iRT review] Draft Thick<br>
                    &gt;&gt; Whois Transition Policy for .COM, .NET, and
                    .JOBS<br>
                    &gt;&gt; <br>
                    &gt;&gt; Partially. As the thick whois WG clearly
                    recommended that a legal<br>
                    &gt;&gt; review be undertaken with regard to the
                    impact of any implementation<br>
                    &gt;&gt; on local privacy legislations, the question
                    of available excemptions<br>
                    &gt;&gt; may well become relevant to such a review.<br>
                    &gt;&gt; <br>
                    &gt;&gt; Best,<br>
                    &gt;&gt; <br>
                    &gt;&gt; Volker<br>
                    &gt;&gt; <br>
                    &gt;&gt; Am 07.09.2016 um 16:38 schrieb Metalitz,
                    Steven:<br>
                    &gt;&gt; <br>
                    &gt;&gt; Agree that this issue is outside the scope
                    of this group.<br>
                    &gt;&gt; <br>
                    &gt;&gt; STEVEN J. METALITZ | PARTNER, THROUGH HIS
                    PROFESSIONAL CORPORATION<br>
                    &gt;&gt; <br>
                    &gt;&gt; T: 202.355.7902 | <a
                      moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a><br>
                    &gt;&gt; <br>
                    &gt;&gt; MITCHELL SILBERBERG &amp; KNUPPLLP | <a
                      moz-do-not-send="true" href="http://WWW.MSK.COM">WWW.MSK.COM</a>
                    [2] [1 [3]]<br>
                    &gt;&gt; <br>
                    &gt;&gt; 1818 N Street NW, 8th Floor, Washington, DC
                    20036<br>
                    &gt;&gt; <br>
                    &gt;&gt; THE INFORMATION CONTAINED IN THIS E-MAIL
                    MESSAGE IS INTENDED ONLY<br>
                    &gt;&gt; FOR THE PERSONAL AND CONFIDENTIAL USE OF
                    THE DESIGNATED<br>
                    &gt;&gt; RECIPIENTS. THIS MESSAGE MAY BE AN
                    ATTORNEY-CLIENT COMMUNICATION,<br>
                    &gt;&gt; AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL.
                    IF THE READER OF THIS<br>
                    &gt;&gt; MESSAGE IS NOT AN INTENDED RECIPIENT, YOU
                    ARE HEREBY NOTIFIED THAT<br>
                    &gt;&gt; ANY REVIEW, USE, DISSEMINATION, FORWARDING
                    OR COPYING OF THIS<br>
                    &gt;&gt; MESSAGE IS STRICTLY PROHIBITED. PLEASE
                    NOTIFY US IMMEDIATELY BY<br>
                    &gt;&gt; REPLY E-MAIL OR TELEPHONE, AND DELETE THE
                    ORIGINAL MESSAGE AND ALL<br>
                    &gt;&gt; ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.<br>
                    &gt;&gt; <br>
                    &gt;&gt; FROM: <a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a><br>
                    &gt;&gt; [<a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
                    ON BEHALF OF<br>
                    &gt;&gt; Volker Greimann<br>
                    &gt;&gt; SENT: Wednesday, September 07, 2016 9:28 AM<br>
                    &gt;&gt; TO: gtheo<br>
                    &gt;&gt; CC: <a moz-do-not-send="true"
                      href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt;&gt; SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for
                    iRT review] Draft<br>
                    &gt;&gt; Thick Whois Transition Policy for .COM,
                    .NET, and .JOBS<br>
                    &gt;&gt; <br>
                    &gt;&gt; Well, I agree that we need a workable
                    process for obtaining an<br>
                    &gt;&gt; excemption, but that is a discussion for
                    another group, I guess.<br>
                    &gt;&gt; An<br>
                    &gt;&gt; Implementation Advisory Group, if you will.
                    I hear there may soon<br>
                    &gt;&gt; be<br>
                    &gt;&gt; another one of those. ;-)<br>
                    &gt;&gt; <br>
                    &gt;&gt; Best,<br>
                    &gt;&gt; <br>
                    &gt;&gt; Volker<br>
                    &gt;&gt; <br>
                    &gt;&gt; Am 07.09.2016 um 15:18 schrieb gtheo:<br>
                    &gt;&gt; <br>
                    &gt;&gt; That might be a way forward Volker.<br>
                    &gt;&gt; <br>
                    &gt;&gt; <br>
                    &gt; <a moz-do-not-send="true"
href="https://www.icann.org/resources/pages/waiver-request-process-2013-09-13-en">https://www.icann.org/resources/pages/waiver-request-process-2013-09-13-en</a><br>
                    &gt;&gt; <br>
                    &gt;&gt; <br>
                    &gt;&gt; However, that one wasn't exactly "speedy".
                    Took me two years to<br>
                    &gt;&gt; <br>
                    &gt;&gt; obtain<br>
                    &gt;&gt; <br>
                    &gt;&gt; one.<br>
                    &gt;&gt; The invalidation of Safe Harbor was rather
                    sudden. Some<br>
                    &gt;&gt; <br>
                    &gt;&gt; governments<br>
                    &gt;&gt; <br>
                    &gt;&gt; displayed the last 12 months that things
                    can change at record<br>
                    &gt;&gt; <br>
                    &gt;&gt; speed<br>
                    &gt;&gt; <br>
                    &gt;&gt; law wise.<br>
                    &gt;&gt; <br>
                    &gt;&gt; I guess the problem boils down to this.<br>
                    &gt;&gt; -Sudden changes in law putting migrated
                    Registrar businesses at<br>
                    &gt;&gt; <br>
                    &gt;&gt; risk.<br>
                    &gt;&gt; <br>
                    &gt;&gt; -The procedure can take much longer than
                    the proposed timeline.<br>
                    &gt;&gt; -There might be Registrars that cannot
                    migrate.<br>
                    &gt;&gt; <br>
                    &gt;&gt; I am not sure, but I have the feeling that
                    it is not up to the<br>
                    &gt;&gt; <br>
                    &gt;&gt; IRT to<br>
                    &gt;&gt; <br>
                    &gt;&gt; fix this as it is out of scope.<br>
                    &gt;&gt; Though Registrars who cannot migrate, we
                    might want to mention<br>
                    &gt;&gt; <br>
                    &gt;&gt; RDAP.<br>
                    &gt;&gt; <br>
                    &gt;&gt; Even though that is already mentioned in
                    the RDAP spec when it<br>
                    &gt;&gt; <br>
                    &gt;&gt; comes<br>
                    &gt;&gt; <br>
                    &gt;&gt; to Thin WHOIS Registries.<br>
                    &gt;&gt; <br>
                    &gt;&gt; Theo<br>
                    &gt;&gt; <br>
                    &gt;&gt; Volker Greimann schreef op 2016-09-07 01:24
                    PM:<br>
                    &gt;&gt; <br>
                    &gt;&gt; How about adding: "Further procedures for
                    resolving conflicts<br>
                    &gt;&gt; <br>
                    &gt;&gt; with<br>
                    &gt;&gt; <br>
                    &gt;&gt; local privacy laws are included in the 2013
                    RAA Data Retention<br>
                    &gt;&gt; specification"?<br>
                    &gt;&gt; <br>
                    &gt;&gt; Am 07.09.2016 um 12:52 schrieb gtheo:<br>
                    &gt;&gt; <br>
                    &gt;&gt; Hello all,<br>
                    &gt;&gt; <br>
                    &gt;&gt; _1. Where a conflict exists between local
                    privacy laws and<br>
                    &gt;&gt; requirements included in this Policy,
                    ICANN's Procedure for<br>
                    &gt;&gt; Handling WHOIS Conflicts with Privacy Laws
                    is available for<br>
                    &gt;&gt; <br>
                    &gt;&gt; Registry<br>
                    &gt;&gt; <br>
                    &gt;&gt; Operators and Registrars. _<br>
                    &gt;&gt; <br>
                    &gt;&gt; We didn't get around this yesterday, wich
                    is fine. Let us see<br>
                    &gt;&gt; <br>
                    &gt;&gt; if we<br>
                    &gt;&gt; <br>
                    &gt;&gt; can have some discussion in advance about
                    this as I am<br>
                    &gt;&gt; <br>
                    &gt;&gt; struggling<br>
                    &gt;&gt; <br>
                    &gt;&gt; with this section for a few now.<br>
                    &gt;&gt; <br>
                    &gt;&gt; The text itself is good, as in, this is
                    what I expected after<br>
                    &gt;&gt; <br>
                    &gt;&gt; the<br>
                    &gt;&gt; <br>
                    &gt;&gt; discussions we had about this in the last
                    few months.<br>
                    &gt;&gt; <br>
                    &gt;&gt; What I am not sure off is how to deal with
                    this in the sense of<br>
                    &gt;&gt; moving forward to the comment period.<br>
                    &gt;&gt; The procedure is not working, but is
                    outside of this IRT to<br>
                    &gt;&gt; <br>
                    &gt;&gt; address,<br>
                    &gt;&gt; <br>
                    &gt;&gt; yet this IRT relies on it.<br>
                    &gt;&gt; <br>
                    &gt;&gt; Are we going to put in a footnote in the
                    report that says<br>
                    &gt;&gt; <br>
                    &gt;&gt; something<br>
                    &gt;&gt; <br>
                    &gt;&gt; like:<br>
                    &gt;&gt; _Outside the scope of the IRT to address,
                    but we wish the<br>
                    &gt;&gt; <br>
                    &gt;&gt; Registrars<br>
                    &gt;&gt; <br>
                    &gt;&gt; and Registrants the best of luck!_<br>
                    &gt;&gt; <br>
                    &gt;&gt; Thanks,<br>
                    &gt;&gt; Theo<br>
                    &gt;&gt; <br>
                    &gt;&gt; Dennis Chang schreef op 2016-09-02 02:05
                    AM:<br>
                    &gt;&gt; <br>
                    &gt;&gt; Dear Thick Whois Policy Implementation
                    Review Team,<br>
                    &gt;&gt; <br>
                    &gt;&gt; Attached for your review is our initial
                    draft of the Thick<br>
                    &gt;&gt; <br>
                    &gt;&gt; Whois<br>
                    &gt;&gt; <br>
                    &gt;&gt; Transition Policy for .COM, .NET and .JOBS.
                    The draft Policy<br>
                    &gt;&gt; includes<br>
                    &gt;&gt; the various elements discussed in our
                    recent meeting on this<br>
                    &gt;&gt; topic.<br>
                    &gt;&gt; <br>
                    &gt;&gt; As you review the draft, you will find
                    bracketed text in four<br>
                    &gt;&gt; sections: sections 2.9, 2.10, 3.4 and 3.5.
                    These sections are<br>
                    &gt;&gt; bracketed because they reference the
                    Registry Registration Data<br>
                    &gt;&gt; Directory Services Consistent Labeling and
                    Display Policy and<br>
                    &gt;&gt; <br>
                    &gt;&gt; the<br>
                    &gt;&gt; <br>
                    &gt;&gt; Registration Data Access Protocol gTLD
                    Profile. As you may be<br>
                    &gt;&gt; aware, a<br>
                    &gt;&gt; Request for Reconsideration (RfR) was
                    submitted by the<br>
                    &gt;&gt; <br>
                    &gt;&gt; Registries<br>
                    &gt;&gt; <br>
                    &gt;&gt; Stakeholder Group in August regarding the
                    Registry Registration<br>
                    &gt;&gt; Data<br>
                    &gt;&gt; Directory Services Consistent Labeling and
                    Display Policy [1<br>
                    &gt;&gt; <br>
                    &gt;&gt; [1]]<br>
                    &gt;&gt; <br>
                    &gt;&gt; that was<br>
                    &gt;&gt; published on 26 July 2016. The RfR objects
                    to the inclusion of<br>
                    &gt;&gt; RDAP in<br>
                    &gt;&gt; the Consensus Policy. While the RfR goes
                    through its own<br>
                    &gt;&gt; <br>
                    &gt;&gt; process,<br>
                    &gt;&gt; <br>
                    &gt;&gt; we<br>
                    &gt;&gt; thought it was important to continue
                    progressing the<br>
                    &gt;&gt; implementation<br>
                    &gt;&gt; project with the goal of opening Public
                    Comment in September<br>
                    &gt;&gt; <br>
                    &gt;&gt; and<br>
                    &gt;&gt; <br>
                    &gt;&gt; announcing the Transition Policy by 1
                    February 2017 per our<br>
                    &gt;&gt; schedule.<br>
                    &gt;&gt; Therefore, the text is bracketed as it may
                    need to be revisited<br>
                    &gt;&gt; pending the resolution of the RfR and we
                    wanted to directly<br>
                    &gt;&gt; <br>
                    &gt;&gt; call<br>
                    &gt;&gt; <br>
                    &gt;&gt; the<br>
                    &gt;&gt; IRT's attention to it.<br>
                    &gt;&gt; <br>
                    &gt;&gt; We will review all contents of the document
                    at our next IRT<br>
                    &gt;&gt; meeting as<br>
                    &gt;&gt; a team but please provide your comments in
                    advance via email if<br>
                    &gt;&gt; possible.<br>
                    &gt;&gt; <br>
                    &gt;&gt; Thank you for your support!<br>
                    &gt;&gt; <br>
                    &gt;&gt; --<br>
                    &gt;&gt; <br>
                    &gt;&gt; Kind Regards,<br>
                    &gt;&gt; <br>
                    &gt;&gt; Dennis S. Chang<br>
                    &gt;&gt; <br>
                    &gt;&gt; GDD Services &amp; Engagement Program
                    Director<br>
                    &gt;&gt; <br>
                    &gt;&gt; +1 213 293 7889<br>
                    &gt;&gt; <br>
                    &gt;&gt; Skype: dennisSchang<br>
                    &gt;&gt; <br>
                    &gt;&gt; <a moz-do-not-send="true"
                      href="http://www.icann.org">www.icann.org</a> [4]
                    [2 [4]] [2 [4]] "One World, One Internet"<br>
                    &gt;&gt; <br>
                    &gt;&gt; Links:<br>
                    &gt;&gt; ------<br>
                    &gt;&gt; [1 [3]]<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
href="https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en">https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en</a><br>
                    &gt; <br>
                    &gt; <br>
                    &gt;&gt;
                    _______________________________________________<br>
                    &gt;&gt; Gnso-impl-thickwhois-rt mailing list<br>
                    &gt;&gt; <a moz-do-not-send="true"
                      href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt;&gt; <a moz-do-not-send="true"
                      href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><br>
                    &gt;&gt; <br>
                    &gt;&gt;
                    _______________________________________________<br>
                    &gt;&gt; Gnso-impl-thickwhois-rt mailing list<br>
                    &gt;&gt; <a moz-do-not-send="true"
                      href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt;&gt; <a moz-do-not-send="true"
                      href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><br>
                    &gt; <br>
                    &gt; --<br>
                    &gt; Bei weiteren Fragen stehen wir Ihnen gerne zur
                    Verfügung.<span style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Mit freundlichen Grüßen,<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Volker A. Greimann<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; - Rechtsabteilung -<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Key-Systems GmbH<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Im Oberen Werk 1<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; 66386 St. Ingbert<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Tel.: +49 (0) 6894 - 9396 901<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Fax.: +49 (0) 6894 - 9396 851<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Email: <a moz-do-not-send="true"
                      href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
                    &gt; <br>
                    &gt; Web: <a moz-do-not-send="true"
                      href="http://www.key-systems.net">www.key-systems.net</a>
                    [5] [3 [5]] /
                    <a moz-do-not-send="true"
                      href="http://www.RRPproxy.net">www.RRPproxy.net</a>
                    [6] [4 [6]]<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.domaindiscount24.com">www.domaindiscount24.com</a>
                    [7] [5 [7]] /
                    <a moz-do-not-send="true"
                      href="http://www.BrandShelter.com">www.BrandShelter.com</a>
                    [8] [6<br>
                    &gt; [8]]<br>
                    &gt; <br>
                    &gt; Folgen Sie uns bei Twitter oder werden Sie
                    unser Fan bei Facebook:<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
                    [9] [7 [9]]<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
                    [10] [8 [10]]<br>
                    &gt; <br>
                    &gt; Geschäftsführer: Alexander Siffrin<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Handelsregister Nr.: HR B 18835 -
                    Saarbruecken<span style="font-family:PMingLiU"><br>
                    </span>&gt; Umsatzsteuer ID.: DE211006534<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Member of the KEYDRIVE GROUP<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <a moz-do-not-send="true"
                      href="http://www.keydrive.lu">www.keydrive.lu</a>
                    [11] [9 [11]]<br>
                    &gt; <br>
                    &gt; Der Inhalt dieser Nachricht ist vertraulich und
                    nur für den<span style="font-family:PMingLiU"><br>
                    </span>&gt; angegebenen Empfänger bestimmt. Jede
                    Form der Kenntnisgabe,<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Veröffentlichung oder Weitergabe an
                    Dritte durch den Empfänger<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; ist unzulässig. Sollte diese Nachricht
                    nicht für Sie bestimmt<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; sein, so bitten wir Sie, sich mit uns
                    per E-Mail oder telefonisch<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; in Verbindung zu setzen.<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt;
                    --------------------------------------------<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Should you have any further questions,
                    please do not hesitate to<br>
                    &gt; contact us.<br>
                    &gt; <br>
                    &gt; Best regards,<br>
                    &gt; <br>
                    &gt; Volker A. Greimann<br>
                    &gt; - legal department -<br>
                    &gt; <br>
                    &gt; Key-Systems GmbH<br>
                    &gt; Im Oberen Werk 1<br>
                    &gt; 66386 St. Ingbert<br>
                    &gt; Tel.: +49 (0) 6894 - 9396 901<br>
                    &gt; Fax.: +49 (0) 6894 - 9396 851<br>
                    &gt; Email: <a moz-do-not-send="true"
                      href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
                    &gt; <br>
                    &gt; Web: <a moz-do-not-send="true"
                      href="http://www.key-systems.net">www.key-systems.net</a>
                    [5] [3 [5]] /
                    <a moz-do-not-send="true"
                      href="http://www.RRPproxy.net">www.RRPproxy.net</a>
                    [6] [4 [6]]<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.domaindiscount24.com">www.domaindiscount24.com</a>
                    [7] [5 [7]] /
                    <a moz-do-not-send="true"
                      href="http://www.BrandShelter.com">www.BrandShelter.com</a>
                    [8] [6<br>
                    &gt; [8]]<br>
                    &gt; <br>
                    &gt; Follow us on Twitter or join our fan community
                    on Facebook and<br>
                    &gt; stay updated:<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
                    [9] [7 [9]]<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
                    [10] [8 [10]]<br>
                    &gt; <br>
                    &gt; CEO: Alexander Siffrin<br>
                    &gt; Registration No.: HR B 18835 - Saarbruecken<br>
                    &gt; V.A.T. ID.: DE211006534<br>
                    &gt; <br>
                    &gt; Member of the KEYDRIVE GROUP<br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.keydrive.lu">www.keydrive.lu</a>
                    [11] [9 [11]]<br>
                    &gt; <br>
                    &gt; This e-mail and its attachments is intended
                    only for the person to<br>
                    &gt; whom it is addressed. Furthermore it is not
                    permitted to publish<br>
                    &gt; any content of this email. You must not use,
                    disclose, copy, print<br>
                    &gt; or rely on this e-mail. If an addressing or
                    transmission error has<br>
                    &gt; misdirected this e-mail, kindly notify the
                    author by replying to<br>
                    &gt; this e-mail or contacting us by telephone.<br>
                    &gt; <br>
                    &gt; _______________________________________________<br>
                    &gt; Gnso-impl-thickwhois-rt mailing list<br>
                    &gt; <a moz-do-not-send="true"
                      href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt; <a moz-do-not-send="true"
                      href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><br>
                    &gt; <br>
                    &gt; --<br>
                    &gt; <br>
                    &gt; Bei weiteren Fragen stehen wir Ihnen gerne zur
                    Verfügung.<span style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Mit freundlichen Grüßen,<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Volker A. Greimann<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; - Rechtsabteilung -<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Key-Systems GmbH<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Im Oberen Werk 1<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; 66386 St. Ingbert<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <br>
                    &gt; Tel.: +49 (0) 6894 - 9396 901<br>
                    &gt; <br>
                    &gt; Fax.: +49 (0) 6894 - 9396 851<br>
                    &gt; <br>
                    &gt; Email: <a moz-do-not-send="true"
                      href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
                    &gt; <br>
                    &gt; Web: <a moz-do-not-send="true"
                      href="http://www.key-systems.net">www.key-systems.net</a>
                    [5] [3 [5]] /
                    <a moz-do-not-send="true"
                      href="http://www.RRPproxy.net">www.RRPproxy.net</a>
                    [6] [4 [6]]<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.domaindiscount24.com">www.domaindiscount24.com</a>
                    [7] [5 [7]] /
                    <a moz-do-not-send="true"
                      href="http://www.BrandShelter.com">www.BrandShelter.com</a>
                    [8] [6<br>
                    &gt; [8]]<br>
                    &gt; <br>
                    &gt; Folgen Sie uns bei Twitter oder werden Sie
                    unser Fan bei Facebook:<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
                    [9] [7 [9]]<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
                    [10] [8 [10]]<br>
                    &gt; <br>
                    &gt; Geschäftsführer: Alexander Siffrin<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Handelsregister Nr.: HR B 18835 -
                    Saarbruecken<span style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Umsatzsteuer ID.: DE211006534<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; Member of the KEYDRIVE GROUP<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; <span style="font-family:PMingLiU"><br>
                    </span>&gt; <a moz-do-not-send="true"
                      href="http://www.keydrive.lu">www.keydrive.lu</a>
                    [11] [9 [11]]<br>
                    &gt; <br>
                    &gt; Der Inhalt dieser Nachricht ist vertraulich und
                    nur für den<span style="font-family:PMingLiU"><br>
                    </span>&gt; angegebenen Empfänger bestimmt. Jede
                    Form der Kenntnisgabe,<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; Veröffentlichung oder Weitergabe an
                    Dritte durch den Empfänger ist<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; unzulässig. Sollte diese Nachricht nicht
                    für Sie bestimmt sein, so<span
                      style="font-family:PMingLiU"><br>
                    </span>&gt; bitten wir Sie, sich mit uns per E-Mail
                    oder telefonisch in<br>
                    &gt; Verbindung zu setzen.<br>
                    &gt; <br>
                    &gt; --------------------------------------------<br>
                    &gt; <br>
                    &gt; Should you have any further questions, please
                    do not hesitate to<br>
                    &gt; contact us.<br>
                    &gt; <br>
                    &gt; Best regards,<br>
                    &gt; <br>
                    &gt; Volker A. Greimann<br>
                    &gt; <br>
                    &gt; - legal department -<br>
                    &gt; <br>
                    &gt; Key-Systems GmbH<br>
                    &gt; <br>
                    &gt; Im Oberen Werk 1<br>
                    &gt; <br>
                    &gt; 66386 St. Ingbert<br>
                    &gt; <br>
                    &gt; Tel.: +49 (0) 6894 - 9396 901<br>
                    &gt; <br>
                    &gt; Fax.: +49 (0) 6894 - 9396 851<br>
                    &gt; <br>
                    &gt; Email: <a moz-do-not-send="true"
                      href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
                    &gt; <br>
                    &gt; Web: <a moz-do-not-send="true"
                      href="http://www.key-systems.net">www.key-systems.net</a>
                    [5] [3 [5]] /
                    <a moz-do-not-send="true"
                      href="http://www.RRPproxy.net">www.RRPproxy.net</a>
                    [6] [4 [6]]<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.domaindiscount24.com">www.domaindiscount24.com</a>
                    [7] [5 [7]] /
                    <a moz-do-not-send="true"
                      href="http://www.BrandShelter.com">www.BrandShelter.com</a>
                    [8] [6<br>
                    &gt; [8]]<br>
                    &gt; <br>
                    &gt; Follow us on Twitter or join our fan community
                    on Facebook and stay<br>
                    &gt; updated:<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
                    [9] [7 [9]]<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
                    [10] [8 [10]]<br>
                    &gt; <br>
                    &gt; CEO: Alexander Siffrin<br>
                    &gt; <br>
                    &gt; Registration No.: HR B 18835 - Saarbruecken<br>
                    &gt; <br>
                    &gt; V.A.T. ID.: DE211006534<br>
                    &gt; <br>
                    &gt; Member of the KEYDRIVE GROUP<br>
                    &gt; <br>
                    &gt; <a moz-do-not-send="true"
                      href="http://www.keydrive.lu">www.keydrive.lu</a>
                    [11] [9 [11]]<br>
                    &gt; <br>
                    &gt; This e-mail and its attachments is intended
                    only for the person to<br>
                    &gt; whom it is addressed. Furthermore it is not
                    permitted to publish any<br>
                    &gt; content of this email. You must not use,
                    disclose, copy, print or<br>
                    &gt; rely on this e-mail. If an addressing or
                    transmission error has<br>
                    &gt; misdirected this e-mail, kindly notify the
                    author by replying to<br>
                    &gt; this e-mail or contacting us by telephone.<br>
                    &gt; <br>
                    &gt; Links:<br>
                    &gt; ------<br>
                    &gt; [1] <a moz-do-not-send="true"
                      href="http://www.msk.com/">http://www.msk.com/</a><br>
                    &gt; [2] <a moz-do-not-send="true"
                      href="http://www.icann.org">http://www.icann.org</a><br>
                    &gt; [3] <a moz-do-not-send="true"
                      href="http://www.key-systems.net">http://www.key-systems.net</a><br>
                    &gt; [4] <a moz-do-not-send="true"
                      href="http://www.RRPproxy.net">http://www.RRPproxy.net</a><br>
                    &gt; [5] <a moz-do-not-send="true"
                      href="http://www.domaindiscount24.com">http://www.domaindiscount24.com</a><br>
                    &gt; [6] <a moz-do-not-send="true"
                      href="http://www.BrandShelter.com">http://www.BrandShelter.com</a><br>
                    &gt; [7] <a moz-do-not-send="true"
                      href="http://www.facebook.com/KeySystems">http://www.facebook.com/KeySystems</a><br>
                    &gt; [8] <a moz-do-not-send="true"
                      href="http://www.twitter.com/key_systems">http://www.twitter.com/key_systems</a><br>
                    &gt; [9] <a moz-do-not-send="true"
                      href="http://www.keydrive.lu">http://www.keydrive.lu</a><br>
                    &gt; [10] <a moz-do-not-send="true"
                      href="http://learn.icann.org/courses/gnso">http://learn.icann.org/courses/gnso</a><br>
                    &gt; [11]<br>
                    &gt; <a moz-do-not-send="true"
href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers">http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers</a><br>
                    &gt; _______________________________________________<br>
                    &gt; Gnso-impl-thickwhois-rt mailing list<br>
                    &gt; <a moz-do-not-send="true"
                      href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
                    &gt; <a moz-do-not-send="true"
                      href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><br>
                    &gt; <br>
                    &gt; Links:<br>
                    &gt; ------<br>
                    &gt; [1] <a moz-do-not-send="true"
                      href="http://learn.icann.org/courses/gnso">http://learn.icann.org/courses/gnso</a><br>
                    &gt; [2] <a moz-do-not-send="true"
                      href="http://WWW.MSK.COM">http://WWW.MSK.COM</a><br>
                    &gt; [3] <a moz-do-not-send="true"
                      href="http://www.msk.com/">http://www.msk.com/</a><br>
                    &gt; [4] <a moz-do-not-send="true"
                      href="http://www.icann.org">http://www.icann.org</a><br>
                    &gt; [5] <a moz-do-not-send="true"
                      href="http://www.key-systems.net">http://www.key-systems.net</a><br>
                    &gt; [6] <a moz-do-not-send="true"
                      href="http://www.RRPproxy.net">http://www.RRPproxy.net</a><br>
                    &gt; [7] <a moz-do-not-send="true"
                      href="http://www.domaindiscount24.com">http://www.domaindiscount24.com</a><br>
                    &gt; [8] <a moz-do-not-send="true"
                      href="http://www.BrandShelter.com">http://www.BrandShelter.com</a><br>
                    &gt; [9] <a moz-do-not-send="true"
                      href="http://www.facebook.com/KeySystems">http://www.facebook.com/KeySystems</a><br>
                    &gt; [10] <a moz-do-not-send="true"
                      href="http://www.twitter.com/key_systems">http://www.twitter.com/key_systems</a><br>
                    &gt; [11] <a moz-do-not-send="true"
                      href="http://www.keydrive.lu">http://www.keydrive.lu</a><o:p></o:p></p>
                </div>
              </div>
            </blockquote>
            <p class="MsoNormal"><o:p> </o:p></p>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>