<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">
<p>Interesting review. After reading it I agree with Volker here. <br /><br /> Few things that stood out. <br /><br /> It seems the focus was put on the 95/46/EC Directive (makes sense) but Safe Harbor was not included in. I am not sure if that was intended? I would not be surprised that anyone ever thought that it would be a possibility that it would be invalidated, and what the consequences are. <br /><br /> Anyways, we just need a good procedure for this IRT. The legal review does not address the current impediment, so that is not up to us. <br /><br /> What is up to us, maybe, are the benefits mentioned in the legal review (page5)?<br /><br /> Let me list them: <br /> 1. A thick Whois model offers attractive archival and restoration properties. If a registrar were to go out of business or experience long-term technical failures rendering<br /> them unable to provide service, registries maintaining thick Whois have all the registrant information at hand and could transfer the registrations to a different (or temporary) registrar so that registrants could continue to manage their domain names.<br /><br /> 2. A thick Whois model reduces the degree of variability in display formats.<br /><br /> 3. Establishing requirements such as collecting uniform sets of data, and display standards, improves consistency across all gTLDs at all levels and result in better access to Whois data for all users of Whois databases (e.g. law enforcement, Intellectual Property holders, etc).<br /><br /> 4. The uptime of the registry with respect to Whois data has typically been found to be better (at least marginally) than the registrar. <br /><br /> I am not sure about the rest of you, but this re-enforces the point that this migration has been in the freezer for too long. <br /><br /> Point 1, that's why we have escrow obligations. The reasoning in point 1 is not sustainable for the future I am afraid. <br /> Point 2 and 3, This has been addressed by the RAA 2013 and the AWIP policy released in 2015. <br /> Point 4, I suspect with RDAP this problem will also be solved. Beside the RAA 2013 also addresses this with an SLA. <br /><br /> One could almost argue there are no benefits. Not sure if you guys want to circle back on this one and include this in a side note for the comment period. <br /><br /> Also, interesting to read but, out of scope for this IRT (I think) is the RDAP solution (page 12 of the legal review)? It could be me, but it almost looks like if there was a quick procedure and workable procedure then the technical issue would be solved also, and it would solve our impediment.</p>
<p>Thank you for making it this far. <br /><br /> Theo <br /><br /><br /> theo geurts schreef op 2016-09-07 10:22 PM:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Thanks, Marika,<br /> <br /> I'll give that one a read tomorrow. Though I think Volker is right.<br /> Seems we are operating under old marching orders, Steve already warned<br /> us that this thing has taken way too long. The draft Verisign prepared<br /> does actually highlight the current situation. And to be fair? How<br /> many people would have thought that Safe Harbor would have been<br /> invalidated? Not me for sure. But I also did not predict the brexit or<br /> Trump running for president. <br /> <br /> In addition to this, I think we are in agreement here. It is not up to<br /> this IRT. We can only signal the GNSO that most likely we have a few<br /> impediments. <br /> <br /> Best regards, <br /> <br /> Theo <br /> <br /> On 7-9-2016 16:53, Marika Konings wrote:<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">And it can be found here:<br /> </blockquote>
<a 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&modificationDate=1434138098000&api=v2" target="_blank" rel="noreferrer">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&modificationDate=1434138098000&api=v2</a>.
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><br /> <br /> Best regards,<br /> <br /> Marika<br /> <br /> MARIKA KONINGS<br /> <br /> Senior Policy Director & Team Leader for the GNSO, Internet<br /> Corporation for Assigned Names and Numbers (ICANN)<br /> <br /> Email: <a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a><br /> <br /> _ _<br /> <br /> _Follow the GNSO via Twitter @ICANN_GNSO_<br /> <br /> _Find out more about the GNSO by taking our interactive courses [<a href="http://learn.icann.org/courses/gnso" target="_blank" rel="noreferrer">10</a>]<br /> and visiting the GNSO Newcomer pages [11]._<br /> <br /> FROM: <<a href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>> on behalf of<br /> "Metalitz, Steven" <<a href="mailto:met@msk.com">met@msk.com</a>><br /> DATE: Wednesday 7 September 2016 at 08:44<br /> TO: 'Volker Greimann' <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>>, gtheo<br /> <<a href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>><br /> CC: "<a href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a>"<br /> <<a href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a>><br /> SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for iRT review] Draft Thick<br /> Whois Transition Policy for .COM, .NET, and .JOBS<br /> <br /> That legal review was undertaken more than a year ago.<br /> <br /> STEVEN J. METALITZ | PARTNER, THROUGH HIS PROFESSIONAL CORPORATION<br /> <br /> T: 202.355.7902 | <a href="mailto:met@msk.com">met@msk.com</a><br /> <br /> MITCHELL SILBERBERG & KNUPP LLP | <a href="http://WWW.MSK.COM" target="_blank" rel="noreferrer">WWW.MSK.COM</a> [<a href="http://www.msk.com/" target="_blank" rel="noreferrer">1</a>]<br /> <br /> 1818 N Street NW, 8th Floor, Washington, DC 20036<br /> <br /> THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY<br /> FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS.<br /> THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS<br /> PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN<br /> INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE,<br /> DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY<br /> PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR<br /> TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM<br /> YOUR SYSTEM. THANK YOU.<br /> <br /> FROM: Volker Greimann [mailto:<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>]<br /> SENT: Wednesday, September 07, 2016 10:44 AM<br /> TO: Metalitz, Steven; gtheo<br /> CC: <a href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br /> SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for iRT review] Draft Thick<br /> Whois Transition Policy for .COM, .NET, and .JOBS<br /> <br /> Partially. As the thick whois WG clearly recommended that a legal<br /> review be undertaken with regard to the impact of any implementation<br /> on local privacy legislations, the question of available excemptions<br /> may well become relevant to such a review.<br /> <br /> Best,<br /> <br /> Volker<br /> <br /> Am 07.09.2016 um 16:38 schrieb Metalitz, Steven:<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Agree that this issue is outside the scope of this group.<br /> <br /> STEVEN J. METALITZ | PARTNER, THROUGH HIS PROFESSIONAL CORPORATION<br /> <br /> <br /> T: 202.355.7902 | <a href="mailto:met@msk.com">met@msk.com</a><br /> <br /> MITCHELL SILBERBERG & KNUPPLLP | <a href="http://WWW.MSK.COM" target="_blank" rel="noreferrer">WWW.MSK.COM</a> [<a href="http://www.msk.com/" target="_blank" rel="noreferrer">1</a>]<br /> <br /> 1818 N Street NW, 8th Floor, Washington, DC 20036<br /> <br /> THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY<br /> FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED<br /> RECIPIENTS. THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION,<br /> AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS<br /> MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT<br /> ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS<br /> MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY<br /> REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL<br /> ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.<br /> <br /> FROM: <a href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a><br /> [mailto:<a href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>] ON BEHALF OF<br /> Volker Greimann<br /> SENT: Wednesday, September 07, 2016 9:28 AM<br /> TO: gtheo<br /> CC: <a href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br /> SUBJECT: Re: [Gnso-impl-thickwhois-rt] [for iRT review] Draft<br /> Thick Whois Transition Policy for .COM, .NET, and .JOBS<br /> <br /> Well, I agree that we need a workable process for obtaining an<br /> excemption, but that is a discussion for another group, I guess.<br /> An<br /> Implementation Advisory Group, if you will. I hear there may soon<br /> be<br /> another one of those. ;-)<br /> <br /> Best,<br /> <br /> Volker<br /> <br /> Am 07.09.2016 um 15:18 schrieb gtheo:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">That might be a way forward Volker.<br /> <br /> </blockquote>
</blockquote>
</blockquote>
<a href="https://www.icann.org/resources/pages/waiver-request-process-2013-09-13-en" target="_blank" rel="noreferrer">https://www.icann.org/resources/pages/waiver-request-process-2013-09-13-en</a>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><br /> <br /> However, that one wasn't exactly "speedy". Took me two years to</blockquote>
obtain
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">one.<br /> The invalidation of Safe Harbor was rather sudden. Some</blockquote>
governments
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">displayed the last 12 months that things can change at record</blockquote>
speed
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">law wise.<br /> <br /> I guess the problem boils down to this.<br /> -Sudden changes in law putting migrated Registrar businesses at</blockquote>
risk.
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">-The procedure can take much longer than the proposed timeline.<br /> -There might be Registrars that cannot migrate.<br /> <br /> I am not sure, but I have the feeling that it is not up to the</blockquote>
IRT to
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">fix this as it is out of scope.<br /> Though Registrars who cannot migrate, we might want to mention</blockquote>
RDAP.
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Even though that is already mentioned in the RDAP spec when it</blockquote>
comes
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">to Thin WHOIS Registries.<br /> <br /> Theo<br /> <br /> <br /> <br /> <br /> <br /> <br /> Volker Greimann schreef op 2016-09-07 01:24 PM:<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">How about adding: "Further procedures for resolving conflicts</blockquote>
</blockquote>
with
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">local privacy laws are included in the 2013 RAA Data Retention<br /> specification"?<br /> <br /> Am 07.09.2016 um 12:52 schrieb gtheo:<br /> <br /> Hello all,<br /> <br /> _1. Where a conflict exists between local privacy laws and<br /> requirements included in this Policy, ICANN's Procedure for<br /> Handling WHOIS Conflicts with Privacy Laws is available for</blockquote>
</blockquote>
Registry
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Operators and Registrars. _<br /> <br /> We didn't get around this yesterday, wich is fine. Let us see</blockquote>
</blockquote>
if we
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">can have some discussion in advance about this as I am</blockquote>
</blockquote>
struggling
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">with this section for a few now.<br /> <br /> The text itself is good, as in, this is what I expected after</blockquote>
</blockquote>
the
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">discussions we had about this in the last few months.<br /> <br /> What I am not sure off is how to deal with this in the sense of<br /> moving forward to the comment period.<br /> The procedure is not working, but is outside of this IRT to</blockquote>
</blockquote>
address,
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">yet this IRT relies on it.<br /> <br /> Are we going to put in a footnote in the report that says</blockquote>
</blockquote>
something
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">like:<br /> _Outside the scope of the IRT to address, but we wish the</blockquote>
</blockquote>
Registrars
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">and Registrants the best of luck!_<br /> <br /> Thanks,<br /> Theo<br /> <br /> Dennis Chang schreef op 2016-09-02 02:05 AM:<br /> <br /> Dear Thick Whois Policy Implementation Review Team,<br /> <br /> Attached for your review is our initial draft of the Thick</blockquote>
</blockquote>
Whois
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Transition Policy for .COM, .NET and .JOBS. The draft Policy<br /> includes<br /> the various elements discussed in our recent meeting on this<br /> topic.<br /> <br /> As you review the draft, you will find bracketed text in four<br /> sections: sections 2.9, 2.10, 3.4 and 3.5. These sections are<br /> bracketed because they reference the Registry Registration Data<br /> Directory Services Consistent Labeling and Display Policy and</blockquote>
</blockquote>
the
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Registration Data Access Protocol gTLD Profile. As you may be<br /> aware, a<br /> Request for Reconsideration (RfR) was submitted by the</blockquote>
</blockquote>
Registries
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Stakeholder Group in August regarding the Registry Registration<br /> Data<br /> Directory Services Consistent Labeling and Display Policy [1</blockquote>
</blockquote>
[1]]
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">that was<br /> published on 26 July 2016. The RfR objects to the inclusion of<br /> RDAP in<br /> the Consensus Policy. While the RfR goes through its own</blockquote>
</blockquote>
process,
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">we<br /> thought it was important to continue progressing the<br /> implementation<br /> project with the goal of opening Public Comment in September</blockquote>
</blockquote>
and
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">announcing the Transition Policy by 1 February 2017 per our<br /> schedule.<br /> Therefore, the text is bracketed as it may need to be revisited<br /> pending the resolution of the RfR and we wanted to directly</blockquote>
</blockquote>
call
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">the<br /> IRT's attention to it.<br /> <br /> We will review all contents of the document at our next IRT<br /> meeting as<br /> a team but please provide your comments in advance via email if<br /> possible.<br /> <br /> Thank you for your support!<br /> <br /> --<br /> <br /> Kind Regards,<br /> <br /> Dennis S. Chang<br /> <br /> GDD Services & Engagement Program Director<br /> <br /> +1 213 293 7889<br /> <br /> Skype: dennisSchang<br /> <br /> <a href="http://www.icann.org" target="_blank" rel="noreferrer">www.icann.org</a> [<a href="http://www.icann.org" target="_blank" rel="noreferrer">2</a>] [<a href="http://www.icann.org" target="_blank" rel="noreferrer">2</a>] "One World, One Internet"<br /> <br /> Links:<br /> ------<br /> [<a href="http://www.msk.com/" target="_blank" rel="noreferrer">1</a>]</blockquote>
<br /> </blockquote>
</blockquote>
</blockquote>
<a href="https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en" target="_blank" rel="noreferrer">https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en</a>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">_______________________________________________<br /> Gnso-impl-thickwhois-rt mailing list<br /> <a href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br /> <a href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></blockquote>
<br /> _______________________________________________<br /> Gnso-impl-thickwhois-rt mailing list<br /> <a href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br /> <a href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></blockquote>
</blockquote>
<br /> --<br /> Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<br /> <br /> Mit freundlichen Grüßen,<br /> <br /> Volker A. Greimann<br /> - Rechtsabteilung -<br /> <br /> Key-Systems GmbH<br /> Im Oberen Werk 1<br /> 66386 St. Ingbert<br /> Tel.: +49 (0) 6894 - 9396 901<br /> Fax.: +49 (0) 6894 - 9396 851<br /> Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br /> <br /> Web: <a href="http://www.key-systems.net" target="_blank" rel="noreferrer">www.key-systems.net</a> [<a href="http://www.key-systems.net" target="_blank" rel="noreferrer">3</a>] / <a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">www.RRPproxy.net</a> [<a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">4</a>]<br /> <a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">www.domaindiscount24.com</a> [<a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">5</a>] / <a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">www.BrandShelter.com</a> [<a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">6</a>]<br /> <br /> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<br /> <a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">www.facebook.com/KeySystems</a> [<a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">7</a>]<br /> <a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">www.twitter.com/key_systems</a> [<a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">8</a>]<br /> <br /> Geschäftsführer: Alexander Siffrin<br /> Handelsregister Nr.: HR B 18835 - Saarbruecken<br /> Umsatzsteuer ID.: DE211006534<br /> <br /> Member of the KEYDRIVE GROUP<br /> <a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">www.keydrive.lu</a> [<a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">9</a>]<br /> <br /> Der Inhalt dieser Nachricht ist vertraulich und nur für den<br /> angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe,<br /> Veröffentlichung oder Weitergabe an Dritte durch den Empfänger<br /> ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt<br /> sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch<br /> in Verbindung zu setzen.<br /> <br /> --------------------------------------------<br /> <br /> Should you have any further questions, please do not hesitate to<br /> contact us.<br /> <br /> Best regards,<br /> <br /> Volker A. Greimann<br /> - legal department -<br /> <br /> Key-Systems GmbH<br /> Im Oberen Werk 1<br /> 66386 St. Ingbert<br /> Tel.: +49 (0) 6894 - 9396 901<br /> Fax.: +49 (0) 6894 - 9396 851<br /> Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br /> <br /> Web: <a href="http://www.key-systems.net" target="_blank" rel="noreferrer">www.key-systems.net</a> [<a href="http://www.key-systems.net" target="_blank" rel="noreferrer">3</a>] / <a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">www.RRPproxy.net</a> [<a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">4</a>]<br /> <a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">www.domaindiscount24.com</a> [<a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">5</a>] / <a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">www.BrandShelter.com</a> [<a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">6</a>]<br /> <br /> Follow us on Twitter or join our fan community on Facebook and<br /> stay updated:<br /> <a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">www.facebook.com/KeySystems</a> [<a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">7</a>]<br /> <a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">www.twitter.com/key_systems</a> [<a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">8</a>]<br /> <br /> CEO: Alexander Siffrin<br /> Registration No.: HR B 18835 - Saarbruecken<br /> V.A.T. ID.: DE211006534<br /> <br /> Member of the KEYDRIVE GROUP<br /> <a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">www.keydrive.lu</a> [<a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">9</a>]<br /> <br /> This e-mail and its attachments is intended only for the person to<br /> whom it is addressed. Furthermore it is not permitted to publish<br /> any content of this email. You must not use, disclose, copy, print<br /> or rely on this e-mail. If an addressing or transmission error has<br /> misdirected this e-mail, kindly notify the author by replying to<br /> this e-mail or contacting us by telephone.<br /> <br /> _______________________________________________<br /> Gnso-impl-thickwhois-rt mailing list<br /> <a href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br /> <a href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></blockquote>
<br /> --<br /> <br /> Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<br /> <br /> Mit freundlichen Grüßen,<br /> <br /> Volker A. Greimann<br /> <br /> - Rechtsabteilung -<br /> <br /> Key-Systems GmbH<br /> <br /> Im Oberen Werk 1<br /> <br /> 66386 St. Ingbert<br /> <br /> Tel.: +49 (0) 6894 - 9396 901<br /> <br /> Fax.: +49 (0) 6894 - 9396 851<br /> <br /> Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br /> <br /> Web: <a href="http://www.key-systems.net" target="_blank" rel="noreferrer">www.key-systems.net</a> [<a href="http://www.key-systems.net" target="_blank" rel="noreferrer">3</a>] / <a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">www.RRPproxy.net</a> [<a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">4</a>]<br /> <br /> <a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">www.domaindiscount24.com</a> [<a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">5</a>] / <a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">www.BrandShelter.com</a> [<a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">6</a>]<br /> <br /> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<br /> <br /> <a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">www.facebook.com/KeySystems</a> [<a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">7</a>]<br /> <br /> <a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">www.twitter.com/key_systems</a> [<a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">8</a>]<br /> <br /> Geschäftsführer: Alexander Siffrin<br /> <br /> Handelsregister Nr.: HR B 18835 - Saarbruecken<br /> <br /> Umsatzsteuer ID.: DE211006534<br /> <br /> Member of the KEYDRIVE GROUP<br /> <br /> <a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">www.keydrive.lu</a> [<a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">9</a>]<br /> <br /> Der Inhalt dieser Nachricht ist vertraulich und nur für den<br /> angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe,<br /> Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist<br /> unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so<br /> bitten wir Sie, sich mit uns per E-Mail oder telefonisch in<br /> Verbindung zu setzen.<br /> <br /> --------------------------------------------<br /> <br /> Should you have any further questions, please do not hesitate to<br /> contact us.<br /> <br /> Best regards,<br /> <br /> Volker A. Greimann<br /> <br /> - legal department -<br /> <br /> Key-Systems GmbH<br /> <br /> Im Oberen Werk 1<br /> <br /> 66386 St. Ingbert<br /> <br /> Tel.: +49 (0) 6894 - 9396 901<br /> <br /> Fax.: +49 (0) 6894 - 9396 851<br /> <br /> Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br /> <br /> Web: <a href="http://www.key-systems.net" target="_blank" rel="noreferrer">www.key-systems.net</a> [<a href="http://www.key-systems.net" target="_blank" rel="noreferrer">3</a>] / <a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">www.RRPproxy.net</a> [<a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">4</a>]<br /> <br /> <a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">www.domaindiscount24.com</a> [<a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">5</a>] / <a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">www.BrandShelter.com</a> [<a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">6</a>]<br /> <br /> Follow us on Twitter or join our fan community on Facebook and stay<br /> updated:<br /> <br /> <a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">www.facebook.com/KeySystems</a> [<a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">7</a>]<br /> <br /> <a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">www.twitter.com/key_systems</a> [<a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">8</a>]<br /> <br /> CEO: Alexander Siffrin<br /> <br /> Registration No.: HR B 18835 - Saarbruecken<br /> <br /> V.A.T. ID.: DE211006534<br /> <br /> Member of the KEYDRIVE GROUP<br /> <br /> <a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">www.keydrive.lu</a> [<a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">9</a>]<br /> <br /> This e-mail and its attachments is intended only for the person to<br /> whom it is addressed. Furthermore it is not permitted to publish any<br /> content of this email. You must not use, disclose, copy, print or<br /> rely on this e-mail. If an addressing or transmission error has<br /> misdirected this e-mail, kindly notify the author by replying to<br /> this e-mail or contacting us by telephone.</blockquote>
<br /> <br /> <br /> Links:<br /> ------<br /> [1] <a href="http://www.msk.com/" target="_blank" rel="noreferrer">http://www.msk.com/</a><br /> [2] <a href="http://www.icann.org" target="_blank" rel="noreferrer">http://www.icann.org</a><br /> [3] <a href="http://www.key-systems.net" target="_blank" rel="noreferrer">http://www.key-systems.net</a><br /> [4] <a href="http://www.RRPproxy.net" target="_blank" rel="noreferrer">http://www.RRPproxy.net</a><br /> [5] <a href="http://www.domaindiscount24.com" target="_blank" rel="noreferrer">http://www.domaindiscount24.com</a><br /> [6] <a href="http://www.BrandShelter.com" target="_blank" rel="noreferrer">http://www.BrandShelter.com</a><br /> [7] <a href="http://www.facebook.com/KeySystems" target="_blank" rel="noreferrer">http://www.facebook.com/KeySystems</a><br /> [8] <a href="http://www.twitter.com/key_systems" target="_blank" rel="noreferrer">http://www.twitter.com/key_systems</a><br /> [9] <a href="http://www.keydrive.lu" target="_blank" rel="noreferrer">http://www.keydrive.lu</a><br /> [10] <a href="http://learn.icann.org/courses/gnso" target="_blank" rel="noreferrer">http://learn.icann.org/courses/gnso</a><br /> [11]<br /> <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers" target="_blank" rel="noreferrer">http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers</a><br /> _______________________________________________<br /> Gnso-impl-thickwhois-rt mailing list<br /> <a href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br /> <a href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></blockquote>
</div>
</body></html>