<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Thanks, <br>
</p>
<p>Then we continue with the next meeting as planned. <br>
</p>
<p>I do request we put this item and the draft memo up for
discussion also. Not sure if we get to it, if not, no biggie, we
discuss it later. <br>
</p>
<p>But it is imperative that it needs to be discussed. <br>
</p>
<p>Thanks, <br>
</p>
<p>Theo <br>
</p>
<div class="moz-cite-prefix">On 3-9-2016 22:24, Metalitz, Steven
wrote:<br>
</div>
<blockquote
cite="mid:E5B4A2ED43DFAE4F9E710FA54FEF8F62601D93A5@LAEX02.MSK.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (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:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">To
clarify: The Whois conflicts procedure remains unchanged.
It is the proposed change to the procedure (relaxation of
the trigger requirement) that remains in limbo. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"><img
id="Picture_x0020_1"
src="cid:part1.2D2E0383.AFB15166@xs4all.nl"
alt="image001" height="41" width="124"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Steven
J. Metalitz
</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">|<b>
</b></span><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Partner,
through his professional corporation<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">T:
202.355.7902
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">|</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><a
moz-do-not-send="true" href="mailto:met@msk.com"><span
style="color:black">met@msk.com</span></a></span><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#88162E">Mitchell
Silberberg & Knupp</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"></span><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:#88162E">LLP</span></b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">|</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
<b><a moz-do-not-send="true" href="http://www.msk.com/"><span
style="color:#84162E">www.msk.com</span></a><o:p></o:p></b></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">1818
N Street NW, 8th Floor, Washington, DC 20036<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><u><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";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","sans-serif";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><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:gray"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>theo geurts<br>
<b>Sent:</b> Saturday, September 03, 2016 3:15 PM<br>
<b>To:</b> Dennis Chang<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" 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>
<p class="MsoNormal">Hi Dennis,<br>
<br>
Yes, agreed on the implementation project, we are almost there
anyways.<br>
<br>
You are correct that there is no change in the procedure at
this very <br>
moment. But this can change.<br>
<br>
My read is, the WHOIS IAG is in limbo due to the withdrawal.
But it can <br>
be rewritten/reintroduced at the GNSO next meeting, or
thereafter.<br>
<br>
Regardless what they are going to do, I guess we need some
clarity here <br>
and the IRT should signal them?<br>
<br>
Thanks,<br>
<br>
Theo<br>
<br>
<br>
On 2-9-2016 23:11, Dennis Chang wrote:<br>
> Hi Theo,<br>
><br>
> Thanks for your attention to this CP. Much appreciated of
course.<br>
><br>
> My understanding is that the GNSO Council considered a
possible modification to the existing procedure as recommended
by the IAG,<br>
> but this decision has been deferred. Therefore, no change
to the procedure that is currently in place.<br>
><br>
> In another word, we continue with our implementation
project. Agreed?<br>
><br>
> Thanks<br>
> Dennis Chang<br>
><br>
><br>
> On 9/2/16, 1:13 PM, "theo geurts" <<a
moz-do-not-send="true" href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>>
wrote:<br>
><br>
> Hi Dennis,<br>
> <br>
> It just dawned on me that this thing was rather familiar
for two<br>
> reasons. I was an observer on that group and it was
discussed yesterday<br>
> at the GNSO council meeting.<br>
> <br>
> <a moz-do-not-send="true"
href="https://gnso.icann.org/en/meetings/transcript-council-01sep16-en.pdf">https://gnso.icann.org/en/meetings/transcript-council-01sep16-en.pdf</a><br>
> <br>
> The motion is currently withdrawn. Where does that leave
us draft wise?<br>
> <br>
> Side note for those who are interested. The trigger
mentioned in the<br>
> WHOIS IAG was already tried by the Dutch Registry SIDN
(backend operator<br>
> for .Amsterdam) in 2015. The Dutch Privacy Data Regulator
simply replied<br>
> back :"You know the law, stick to it, we are not going to
issue a<br>
> statement". And that was the end of that. Yes, fun people
for sure, they<br>
> just don't how to party.<br>
> <br>
> Anyhow, all fun talk aside, the WHOIS IAG report is not
an option for<br>
> now since it is in limbo at the GNSO, how do we proceed?<br>
> <br>
> Best regards,<br>
> <br>
> Theo<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On 2-9-2016 20:00, theo geurts wrote:<br>
> > Thank you Dennis,<br>
> ><br>
> > I'll give it a read as soon I have the time.<br>
> ><br>
> > Theo<br>
> ><br>
> > On 2-9-2016 15:47, Dennis Chang wrote:<br>
> >> Hello Theo,<br>
> >><br>
> >> ICANN Procedure For Handling WHOIS Conflicts
with Privacy Law<br>
> >> mentioned in the implementation note can be
found here:<br>
> >> <a moz-do-not-send="true"
href="https://whois.icann.org/en/icann-procedure-handling-whois-conflicts-privacy-law">https://whois.icann.org/en/icann-procedure-handling-whois-conflicts-privacy-law</a><br>
> >><br>
> >><br>
> >><br>
> >> Thanks<br>
> >> Dennis Chang<br>
> >><br>
> >><br>
> >> On 9/2/16, 2:19 AM, "gtheo" <<a
moz-do-not-send="true" href="mailto:gtheo@xs4all.nl">gtheo@xs4all.nl</a>>
wrote:<br>
> >><br>
> >> Thanks Dennis,<br>
> >> One question after a quick read, what procedure
is that on the<br>
> >> implementation notes on the last page? Do you
have a link?<br>
> >> For the rest I think we got it covered and
should be able<br>
> >> to wrap it up<br>
> >> rather quickly.<br>
> >> Best regards,<br>
> >> Theo<br>
> >> Dennis Chang schreef op 2016-09-02 02:05 AM:<br>
> >> > Dear Thick Whois Policy Implementation
Review Team,<br>
> >> ><br>
> >> > Attached for your review is our initial
draft of the Thick Whois<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 the<br>
> >> > Registration Data Access Protocol gTLD
Profile. As you may be<br>
> >> aware, a<br>
> >> > Request for Reconsideration (RfR) was
submitted by the Registries<br>
> >> > Stakeholder Group in August regarding the
Registry<br>
> >> Registration Data<br>
> >> > Directory Services Consistent Labeling and
Display Policy [1]<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>
> >> process, we<br>
> >> > thought it was important to continue
progressing the<br>
> >> implementation<br>
> >> > project with the goal of opening Public
Comment in September and<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>
> >> call 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> "One World,
One Internet"<br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> > Links:<br>
> >> > ------<br>
> >> > [1]<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>
> >> > 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>
> > _______________________________________________<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>
><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><o:p></o:p></p>
</div>
</blockquote>
<br>
</body>
</html>