<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"><gtheo@xs4all.nl></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"><dennis.chang@icann.org></a>,
"Metalitz, Steven" <a class="moz-txt-link-rfc2396E" href="mailto:met@msk.com"><met@msk.com></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"><gnso-impl-thickwhois-rt@icann.org></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
"Times New Roman"">
</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
"Times New Roman"">
</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
"Times New Roman"">
</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
"Times New Roman"">
</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
"Times New Roman"">
</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
"Times New Roman"">
</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
"Times New Roman"">
</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"><gnso-impl-thickwhois-rt-bounces@icann.org></a>
on behalf of "Metalitz, Steven"
<a moz-do-not-send="true" href="mailto:met@msk.com"><met@msk.com></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"><gtheo@xs4all.nl></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"><gnso-impl-thickwhois-rt@icann.org></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 & 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>
> Theo’s ruminations lead me to repeat the
questions I posed to Marc<span
style="font-family:PMingLiU"><br>
</span>> last week about his draft memo:<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> (1) The first two developments to which
you cite are the<br>
> invalidation of the US-EU Safe Harbor Program
and the adoption of the<br>
> EU-US Privacy Shield framework to replace it.
My impression is that<br>
> US registries generally did not rely upon the
Safe Harbor in<br>
> processing thick Whois data (e.g., receiving
Whois data containing<br>
> personally identifiable information from
European registrars and<br>
> making it available through registry Whois),
and so would not have<br>
> been directly impacted by its invalidation. Is
my impression wrong?<br>
> If I am correct then what is the relevance of
either the Safe Harbor<br>
> or the Privacy Shield in this context?<br>
> <br>
> (2) The last paragraph refers to data
localization laws apart from<br>
> EU privacy/data protection laws. Can you be
more specific? I note<br>
> that the Russian law was referenced in
footnotes 2 and 10 of the legal<br>
> review provided to the IRT in June 2015, are
there other issues not<br>
> covered by that analysis?<br>
> <br>
> (3) If the IRT were to send this letter, the
GNSO council might<br>
> well ask what (if anything) we are asking them
to do. How would you<br>
> respond?<br>
> <br>
> In particular, If I understand Theo correctly,
his answer to #3 would<br>
> be “please tear up the consensus policy
recommended by the Working<span
style="font-family:PMingLiU"><br>
</span>> Group, adopted by the GNSO Council, and
approved by the ICANN board,<span
style="font-family:PMingLiU"><br>
</span>> it is obsolete, and let’s not waste
[further] time implementing<span
style="font-family:PMingLiU"><br>
</span>> it.” Is that reading correct, and do
others in the IRT support<span
style="font-family:PMingLiU"><br>
</span>> that?<span style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> STEVEN J. METALITZ | PARTNER, THROUGH
HIS PROFESSIONAL CORPORATION<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> T: 202.355.7902 | <a
moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a><br>
> <br>
> MITCHELL SILBERBERG & KNUPP LLP | <a
moz-do-not-send="true" href="http://WWW.MSK.COM">WWW.MSK.COM</a>
[3]<br>
> <br>
> 1818 N Street NW, 8th Floor, Washington, DC
20036<br>
> <br>
> THE INFORMATION CONTAINED IN THIS E-MAIL
MESSAGE IS INTENDED ONLY FOR<br>
> THE PERSONAL AND CONFIDENTIAL USE OF THE
DESIGNATED RECIPIENTS. THIS<br>
> 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 TELEPHONE,<br>
> AND DELETE THE ORIGINAL MESSAGE AND ALL
ATTACHMENTS FROM YOUR SYSTEM.<br>
> THANK YOU.<br>
> <br>
> FROM: gtheo [<a moz-do-not-send="true"
href="mailto:gtheo@xs4all.nl">mailto:gtheo@xs4all.nl</a>]<br>
> SENT: Thursday, September 08, 2016 6:57 AM<br>
> TO: Marika Konings; Metalitz, Steven; 'Volker
Greimann'<br>
> CC: <a moz-do-not-send="true"
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>
> 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<br>
> Safe Harbor was not included in. I am not sure
if that was intended? I<br>
> would not be surprised that anyone ever thought
that it would be a<br>
> possibility that it would be invalidated, and
what the consequences<br>
> are.<br>
> <br>
> Anyways, we just need a good procedure for this
IRT. The legal review<br>
> 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<br>
> review (page5)?<br>
> <br>
> Let me list them:<br>
> 1. A thick Whois model offers attractive
archival and restoration<br>
> properties. If a registrar were to go out of
business or experience<br>
> long-term technical failures rendering<br>
> them unable to provide service, registries
maintaining thick Whois<br>
> have all the registrant information at hand and
could transfer the<br>
> registrations to a different (or temporary)
registrar so that<br>
> registrants could continue to manage their
domain names.<br>
> <br>
> 2. A thick Whois model reduces the degree of
variability in display<br>
> formats.<br>
> <br>
> 3. Establishing requirements such as collecting
uniform sets of<br>
> data, and display standards, improves
consistency across all gTLDs at<br>
> all levels and result in better access to Whois
data for all users of<br>
> Whois databases (e.g. law enforcement,
Intellectual Property holders,<br>
> etc).<br>
> <br>
> 4. The uptime of the registry with respect to
Whois data has<br>
> typically been found to be better (at least
marginally) than the<br>
> registrar.<br>
> <br>
> I am not sure about the rest of you, but this
re-enforces the point<br>
> 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<br>
> 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<br>
> policy released in 2015.<br>
> Point 4, I suspect with RDAP this problem will
also be solved.<br>
> 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<br>
> want to circle back on this one and include
this in a side note for<br>
> the comment period.<br>
> <br>
> Also, interesting to read but, out of scope for
this IRT (I think) is<br>
> the RDAP solution (page 12 of the legal
review)? It could be me, but<br>
> it almost looks like if there was a quick
procedure and workable<br>
> procedure then the technical issue would be
solved also, and it would<br>
> solve our impediment.<br>
> <br>
> Thank you for making it this far.<br>
> <br>
> Theo<br>
> <br>
> theo geurts schreef op 2016-09-07 10:22 PM:<br>
> <br>
>> 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<br>
>> warned<br>
>> us that this thing has taken way too long.
The draft Verisign<br>
>> 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<br>
>> or<br>
>> Trump running for president.<br>
>> <br>
>> In addition to this, I think we are in
agreement here. It is not up<br>
>> to<br>
>> this IRT. We can only signal the GNSO that
most likely we have a<br>
>> few<br>
>> impediments.<br>
>> <br>
>> Best regards,<br>
>> <br>
>> Theo<br>
>> <br>
>> On 7-9-2016 16:53, Marika Konings wrote:<br>
>> <br>
>> And it can be found here:<br>
>> <br>
>> <br>
> <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&modificationDate=1434138098000&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&modificationDate=1434138098000&api=v2</a>.<br>
>> <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 moz-do-not-send="true"
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 [10<br>
>> [1]]<br>
>> and visiting the GNSO Newcomer pages [11]._<br>
>> <br>
>> FROM: <<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>>
on behalf of<br>
>> "Metalitz, Steven" <<a
moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a>><br>
>> DATE: Wednesday 7 September 2016 at 08:44<br>
>> TO: 'Volker Greimann' <<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>>,
gtheo<br>
>> <<a moz-do-not-send="true"
href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>><br>
>> CC: "<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a>"<br>
>> <<a moz-do-not-send="true"
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
moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a><br>
>> <br>
>> MITCHELL SILBERBERG & KNUPP LLP | <a
moz-do-not-send="true" href="http://WWW.MSK.COM">WWW.MSK.COM</a>
[2] [1 [3]]<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 [<a
moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">mailto:vgreimann@key-systems.net</a>]<br>
>> SENT: Wednesday, September 07, 2016 10:44
AM<br>
>> TO: Metalitz, Steven; gtheo<br>
>> CC: <a moz-do-not-send="true"
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>
>> Agree that this issue is outside the scope
of this group.<br>
>> <br>
>> STEVEN J. METALITZ | PARTNER, THROUGH HIS
PROFESSIONAL CORPORATION<br>
>> <br>
>> T: 202.355.7902 | <a
moz-do-not-send="true" href="mailto:met@msk.com">met@msk.com</a><br>
>> <br>
>> MITCHELL SILBERBERG & KNUPPLLP | <a
moz-do-not-send="true" href="http://WWW.MSK.COM">WWW.MSK.COM</a>
[2] [1 [3]]<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 moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a><br>
>> [<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>
>> Volker Greimann<br>
>> SENT: Wednesday, September 07, 2016 9:28 AM<br>
>> TO: gtheo<br>
>> CC: <a moz-do-not-send="true"
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:<br>
>> <br>
>> That might be a way forward Volker.<br>
>> <br>
>> <br>
> <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>
>> <br>
>> <br>
>> However, that one wasn't exactly "speedy".
Took me two years to<br>
>> <br>
>> obtain<br>
>> <br>
>> one.<br>
>> The invalidation of Safe Harbor was rather
sudden. Some<br>
>> <br>
>> governments<br>
>> <br>
>> displayed the last 12 months that things
can change at record<br>
>> <br>
>> speed<br>
>> <br>
>> law wise.<br>
>> <br>
>> I guess the problem boils down to this.<br>
>> -Sudden changes in law putting migrated
Registrar businesses at<br>
>> <br>
>> risk.<br>
>> <br>
>> -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<br>
>> <br>
>> IRT to<br>
>> <br>
>> fix this as it is out of scope.<br>
>> Though Registrars who cannot migrate, we
might want to mention<br>
>> <br>
>> RDAP.<br>
>> <br>
>> Even though that is already mentioned in
the RDAP spec when it<br>
>> <br>
>> comes<br>
>> <br>
>> to Thin WHOIS Registries.<br>
>> <br>
>> Theo<br>
>> <br>
>> Volker Greimann schreef op 2016-09-07 01:24
PM:<br>
>> <br>
>> How about adding: "Further procedures for
resolving conflicts<br>
>> <br>
>> with<br>
>> <br>
>> 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<br>
>> <br>
>> Registry<br>
>> <br>
>> Operators and Registrars. _<br>
>> <br>
>> We didn't get around this yesterday, wich
is fine. Let us see<br>
>> <br>
>> if we<br>
>> <br>
>> can have some discussion in advance about
this as I am<br>
>> <br>
>> struggling<br>
>> <br>
>> with this section for a few now.<br>
>> <br>
>> The text itself is good, as in, this is
what I expected after<br>
>> <br>
>> the<br>
>> <br>
>> 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<br>
>> <br>
>> address,<br>
>> <br>
>> yet this IRT relies on it.<br>
>> <br>
>> Are we going to put in a footnote in the
report that says<br>
>> <br>
>> something<br>
>> <br>
>> like:<br>
>> _Outside the scope of the IRT to address,
but we wish the<br>
>> <br>
>> Registrars<br>
>> <br>
>> 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<br>
>> <br>
>> Whois<br>
>> <br>
>> 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<br>
>> <br>
>> the<br>
>> <br>
>> Registration Data Access Protocol gTLD
Profile. As you may be<br>
>> aware, a<br>
>> Request for Reconsideration (RfR) was
submitted by the<br>
>> <br>
>> Registries<br>
>> <br>
>> Stakeholder Group in August regarding the
Registry Registration<br>
>> Data<br>
>> Directory Services Consistent Labeling and
Display Policy [1<br>
>> <br>
>> [1]]<br>
>> <br>
>> 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<br>
>> <br>
>> process,<br>
>> <br>
>> we<br>
>> thought it was important to continue
progressing the<br>
>> implementation<br>
>> project with the goal of opening Public
Comment in September<br>
>> <br>
>> and<br>
>> <br>
>> 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<br>
>> <br>
>> call<br>
>> <br>
>> 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 moz-do-not-send="true"
href="http://www.icann.org">www.icann.org</a> [4]
[2 [4]] [2 [4]] "One World, One Internet"<br>
>> <br>
>> Links:<br>
>> ------<br>
>> [1 [3]]<br>
> <br>
> <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>
> <br>
> <br>
>>
_______________________________________________<br>
>> Gnso-impl-thickwhois-rt mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
>> <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>
>> <br>
>>
_______________________________________________<br>
>> Gnso-impl-thickwhois-rt mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
>> <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>
> <br>
> --<br>
> Bei weiteren Fragen stehen wir Ihnen gerne zur
Verfügung.<span style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Mit freundlichen Grüßen,<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Volker A. Greimann<span
style="font-family:PMingLiU"><br>
</span>> - Rechtsabteilung -<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Key-Systems GmbH<span
style="font-family:PMingLiU"><br>
</span>> Im Oberen Werk 1<span
style="font-family:PMingLiU"><br>
</span>> 66386 St. Ingbert<span
style="font-family:PMingLiU"><br>
</span>> Tel.: +49 (0) 6894 - 9396 901<span
style="font-family:PMingLiU"><br>
</span>> Fax.: +49 (0) 6894 - 9396 851<span
style="font-family:PMingLiU"><br>
</span>> Email: <a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
> <br>
> 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>
> <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>
> [8]]<br>
> <br>
> Folgen Sie uns bei Twitter oder werden Sie
unser Fan bei Facebook:<br>
> <a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
[9] [7 [9]]<br>
> <a moz-do-not-send="true"
href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
[10] [8 [10]]<br>
> <br>
> Geschäftsführer: Alexander Siffrin<span
style="font-family:PMingLiU"><br>
</span>> Handelsregister Nr.: HR B 18835 -
Saarbruecken<span style="font-family:PMingLiU"><br>
</span>> Umsatzsteuer ID.: DE211006534<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Member of the KEYDRIVE GROUP<span
style="font-family:PMingLiU"><br>
</span>> <a moz-do-not-send="true"
href="http://www.keydrive.lu">www.keydrive.lu</a>
[11] [9 [11]]<br>
> <br>
> Der Inhalt dieser Nachricht ist vertraulich und
nur für den<span style="font-family:PMingLiU"><br>
</span>> angegebenen Empfänger bestimmt. Jede
Form der Kenntnisgabe,<span
style="font-family:PMingLiU"><br>
</span>> Veröffentlichung oder Weitergabe an
Dritte durch den Empfänger<span
style="font-family:PMingLiU"><br>
</span>> ist unzulässig. Sollte diese Nachricht
nicht für Sie bestimmt<span
style="font-family:PMingLiU"><br>
</span>> sein, so bitten wir Sie, sich mit uns
per E-Mail oder telefonisch<span
style="font-family:PMingLiU"><br>
</span>> in Verbindung zu setzen.<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>>
--------------------------------------------<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> 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 moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
> <br>
> 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>
> <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>
> [8]]<br>
> <br>
> Follow us on Twitter or join our fan community
on Facebook and<br>
> stay updated:<br>
> <a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
[9] [7 [9]]<br>
> <a moz-do-not-send="true"
href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
[10] [8 [10]]<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 moz-do-not-send="true"
href="http://www.keydrive.lu">www.keydrive.lu</a>
[11] [9 [11]]<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 moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
> <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>
> <br>
> --<br>
> <br>
> Bei weiteren Fragen stehen wir Ihnen gerne zur
Verfügung.<span style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Mit freundlichen Grüßen,<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Volker A. Greimann<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> - Rechtsabteilung -<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Key-Systems GmbH<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Im Oberen Werk 1<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> 66386 St. Ingbert<span
style="font-family:PMingLiU"><br>
</span>> <br>
> Tel.: +49 (0) 6894 - 9396 901<br>
> <br>
> Fax.: +49 (0) 6894 - 9396 851<br>
> <br>
> Email: <a moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
> <br>
> 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>
> <br>
> <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>
> [8]]<br>
> <br>
> Folgen Sie uns bei Twitter oder werden Sie
unser Fan bei Facebook:<br>
> <br>
> <a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
[9] [7 [9]]<br>
> <br>
> <a moz-do-not-send="true"
href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
[10] [8 [10]]<br>
> <br>
> Geschäftsführer: Alexander Siffrin<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Handelsregister Nr.: HR B 18835 -
Saarbruecken<span style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Umsatzsteuer ID.: DE211006534<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> Member of the KEYDRIVE GROUP<span
style="font-family:PMingLiU"><br>
</span>> <span style="font-family:PMingLiU"><br>
</span>> <a moz-do-not-send="true"
href="http://www.keydrive.lu">www.keydrive.lu</a>
[11] [9 [11]]<br>
> <br>
> Der Inhalt dieser Nachricht ist vertraulich und
nur für den<span style="font-family:PMingLiU"><br>
</span>> angegebenen Empfänger bestimmt. Jede
Form der Kenntnisgabe,<span
style="font-family:PMingLiU"><br>
</span>> Veröffentlichung oder Weitergabe an
Dritte durch den Empfänger ist<span
style="font-family:PMingLiU"><br>
</span>> unzulässig. Sollte diese Nachricht nicht
für Sie bestimmt sein, so<span
style="font-family:PMingLiU"><br>
</span>> 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 moz-do-not-send="true"
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><br>
> <br>
> 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>
> <br>
> <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>
> [8]]<br>
> <br>
> Follow us on Twitter or join our fan community
on Facebook and stay<br>
> updated:<br>
> <br>
> <a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
[9] [7 [9]]<br>
> <br>
> <a moz-do-not-send="true"
href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
[10] [8 [10]]<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 moz-do-not-send="true"
href="http://www.keydrive.lu">www.keydrive.lu</a>
[11] [9 [11]]<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.<br>
> <br>
> Links:<br>
> ------<br>
> [1] <a moz-do-not-send="true"
href="http://www.msk.com/">http://www.msk.com/</a><br>
> [2] <a moz-do-not-send="true"
href="http://www.icann.org">http://www.icann.org</a><br>
> [3] <a moz-do-not-send="true"
href="http://www.key-systems.net">http://www.key-systems.net</a><br>
> [4] <a moz-do-not-send="true"
href="http://www.RRPproxy.net">http://www.RRPproxy.net</a><br>
> [5] <a moz-do-not-send="true"
href="http://www.domaindiscount24.com">http://www.domaindiscount24.com</a><br>
> [6] <a moz-do-not-send="true"
href="http://www.BrandShelter.com">http://www.BrandShelter.com</a><br>
> [7] <a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems">http://www.facebook.com/KeySystems</a><br>
> [8] <a moz-do-not-send="true"
href="http://www.twitter.com/key_systems">http://www.twitter.com/key_systems</a><br>
> [9] <a moz-do-not-send="true"
href="http://www.keydrive.lu">http://www.keydrive.lu</a><br>
> [10] <a moz-do-not-send="true"
href="http://learn.icann.org/courses/gnso">http://learn.icann.org/courses/gnso</a><br>
> [11]<br>
> <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>
> _______________________________________________<br>
> Gnso-impl-thickwhois-rt mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
> <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>
> <br>
> Links:<br>
> ------<br>
> [1] <a moz-do-not-send="true"
href="http://learn.icann.org/courses/gnso">http://learn.icann.org/courses/gnso</a><br>
> [2] <a moz-do-not-send="true"
href="http://WWW.MSK.COM">http://WWW.MSK.COM</a><br>
> [3] <a moz-do-not-send="true"
href="http://www.msk.com/">http://www.msk.com/</a><br>
> [4] <a moz-do-not-send="true"
href="http://www.icann.org">http://www.icann.org</a><br>
> [5] <a moz-do-not-send="true"
href="http://www.key-systems.net">http://www.key-systems.net</a><br>
> [6] <a moz-do-not-send="true"
href="http://www.RRPproxy.net">http://www.RRPproxy.net</a><br>
> [7] <a moz-do-not-send="true"
href="http://www.domaindiscount24.com">http://www.domaindiscount24.com</a><br>
> [8] <a moz-do-not-send="true"
href="http://www.BrandShelter.com">http://www.BrandShelter.com</a><br>
> [9] <a moz-do-not-send="true"
href="http://www.facebook.com/KeySystems">http://www.facebook.com/KeySystems</a><br>
> [10] <a moz-do-not-send="true"
href="http://www.twitter.com/key_systems">http://www.twitter.com/key_systems</a><br>
> [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>