<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="+1"><font face="Lucida Grande">This sounds like a
good plan Ayden. I issued a dissent on this procedure, and
will be happy to walk people through the process for this
procedure, which the Registrars blocked at the GNSO because
they know it won't work. It has been an unusual
process.....and there is supposed to be a new process starting
in the fall, to come up with something different.<br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-05-05 07:33, Ayden Férdeline
wrote:<br>
</div>
<blockquote
cite="mid:QUbIhyizLkc13xeQGT4Knh7EH6_dqOuGd9B3yLTpuc6yG-fAAu_Mp68LncejBKvOv6JY3K2E6SPYEqu5hZj_4lbsC-kBucxsb3LQZ8x0-3k=@ferdeline.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div>
<div>Hi Rafik,<br>
</div>
<div><br>
</div>
<div>I was thinking of both. <br>
<br>
I think a standalone call is important to engage community
members with no background of the topic. I was thinking that
Stephanie and I (and others if interested) could provide the
members on the call with an introduction first to the issues
at play, then walk them through the comment, and ask focused
questions to understand what members on the call think. I
cannot see this taking less than 60 minutes; if it was a part
of the PC call, it would dominate it. It would also show that
we are responsive to community concerns, given recent
conversations on the list that we do not engage the membership
in our comments.<br>
</div>
<div><br>
</div>
<div>I am happy to update the PC on the policy call as well, but
at a higher-level and only taking 5-10 minutes up of the
meeting. <br>
<br>
Best wishes,</div>
</div>
<div><br>
</div>
<div class="protonmail_signature_block ">
<div class="protonmail_signature_block-user ">
<div>Ayden <br>
</div>
</div>
<div class="protonmail_signature_block-proton
protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<blockquote class="protonmail_quote" type="cite">
<div>-------- Original Message --------<br>
</div>
<div>Subject: Re: [NCSG-PC] Revised ICANN Procedure for Handling
Whois Conflicts with Privacy Law: Assessment and Next Steps
Now Available for Public Comment<br>
</div>
<div>Local Time: May 5, 2017 12:27 PM<br>
</div>
<div>UTC Time: May 5, 2017 11:27 AM<br>
</div>
<div>From: <a class="moz-txt-link-abbreviated" href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a><br>
</div>
<div>To: Ayden Férdeline <a class="moz-txt-link-rfc2396E" href="mailto:icann@ferdeline.com"><icann@ferdeline.com></a><br>
</div>
<div>ncsg-pc <a class="moz-txt-link-rfc2396E" href="mailto:ncsg-pc@lists.ncsg.is"><ncsg-pc@lists.ncsg.is></a><br>
</div>
<div><br>
</div>
<div dir="ltr">
<div class="gmail_extra">Hi Ayden,<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">thanks for volunteering. sharing a
first draft which can be used as a strawman is welcome.<br>
</div>
<div class="gmail_extra">we can schedule either a standalone
call for this topic or put it as an agenda item for the next
NCSG Policy Call in less than 2 weeks. I am in favor of the
former option since it gives more time for discussion and
presentation.<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Best,<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Rafik<br>
</div>
<div class="gmail_extra">
<div><br>
</div>
<div class="gmail_quote">
<div>2017-05-05 19:04 GMT+09:00 Ayden Férdeline <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:icann@ferdeline.com" rel="noreferrer
nofollow noopener">icann@ferdeline.com</a>></span>:<br>
</div>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex" class="gmail_quote">
<div>
<div>Thanks for letting us know that this comment has
opened, Rafik. I am happy to work on a first draft
of this public comment over the weekend, and get it
out to the NCSG list to see what other members
think. <br>
</div>
<div><br>
</div>
<div>As there are still five weeks until comments are
due, it seems like we might have time to schedule a
brief call (for the NCSG membership) where I or
others can walk people through the comment and see,
on the call, if anyone has any suggested edits.<br>
</div>
<div><br>
</div>
<div>Best wishes,<br>
</div>
</div>
<div><br>
</div>
<div
class="m_239849018588204120protonmail_signature_block">
<div
class="m_239849018588204120protonmail_signature_block-user">
<div>Ayden<br>
</div>
</div>
<div
class="m_239849018588204120protonmail_signature_block-proton
m_239849018588204120protonmail_signature_block-empty"><br>
</div>
</div>
<div class="HOEnZb">
<div class="h5">
<div><br>
</div>
<blockquote type="cite"
class="m_239849018588204120protonmail_quote">
<div>-------- Original Message --------<br>
</div>
<div>Subject: [NCSG-PC] Revised ICANN Procedure
for Handling Whois Conflicts with Privacy Law:
Assessment and Next Steps Now Available for
Public Comment<br>
</div>
<div>Local Time: May 5, 2017 10:45 AM<br>
</div>
<div>UTC Time: May 5, 2017 9:45 AM<br>
</div>
<div>From: <a moz-do-not-send="true"
href="mailto:rafik.dammak@gmail.com"
rel="noreferrer nofollow noopener">rafik.dammak@gmail.com</a><br>
</div>
<div>To: <a moz-do-not-send="true"
href="mailto:NCSG-DISCUSS@listserv.syr.edu"
rel="noreferrer nofollow noopener">NCSG-DISCUSS@listserv.syr.edu</a>
<<a moz-do-not-send="true"
href="mailto:NCSG-DISCUSS@listserv.syr.edu"
rel="noreferrer nofollow noopener">NCSG-DISCUSS@listserv.syr.edu</a><wbr>>,
ncsg-pc <<a moz-do-not-send="true"
href="mailto:ncsg-pc@lists.ncsg.is"
rel="noreferrer nofollow noopener">ncsg-pc@lists.ncsg.is</a>><br>
</div>
<div><br>
</div>
<div dir="ltr">
<div>Hi all,<br>
</div>
<div><br>
</div>
<div>we have a new public comment open and I am
sending this as a call for volunteers who want
to take the lead on drafting a NCSG statement.
It is a good opportunity for those with strong
interest on data protection. <br>
</div>
<div><br>
</div>
<div>I think that Stephanie participated in the
group tasked to discuss the Whois conflict
with national laws and she can probably share
some background here.<br>
</div>
<div><br>
</div>
<div>Best,<br>
</div>
<div><br>
</div>
<div>
<div>Rafik<br>
</div>
<div><br>
</div>
<div class="gmail_quote">
<div>---------- Forwarded message ----------<br>
</div>
<div><br>
</div>
<div bgcolor="white" lang="EN-US">
<div
class="m_239849018588204120m_1661760520410877506WordSection1">
<p class="MsoNormal"><span
style="font-family:Calibri"
class="font"><span
style="font-size:11pt"
class="size"> </span></span><br>
</p>
<div style="border:none;border-top:solid
#b5c4df 1.0pt;padding:3.0pt 0in 0in
0in">
<p class="MsoNormal"><b><span
style="color:black"
class="colour"><span
style="font-family:Calibri"
class="font">From: </span></span>
</b><span style="color:black"
class="colour"><span
style="font-family:Calibri"
class="font">ICANN News Alert
<<a moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="mailto:no-reply@external.icann.org">no-reply@external.icann.org</a>><br>
<b>Reply-To: </b>"<a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="mailto:no-reply@external.icann.org">no-reply@external.icann.org</a>"
<<a moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="mailto:no-reply@external.icann.org">no-reply@external.icann.org</a>><br>
<b>Date: </b>Thursday, May 4,
2017 at 01:30<br>
<b>To: </b>Marika Konings <<a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>><br>
<b>Subject: </b>[Ext] ICANN
News Alert -- Revised ICANN
Procedure for Handling Whois
Conflicts with Privacy Law:
Assessment and Next Steps Now
Available for Public Comment</span></span></p>
</div>
<div>
<p class="MsoNormal"> <br>
</p>
</div>
<div style="border:solid #cccccc
1.0pt;padding:8.0pt 8.0pt 8.0pt 8.0pt">
<div>
<p class="MsoNormal"><a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=6V4WSfJlCvfGHagL0A61eO3gp0CdwQGAaDKw_lwpNWo&e="><span
style="text-decoration:none"><img
moz-do-not-send="true"
src="https://www.icann.org/sites/default/files/assets/icann-primary-logo-94x94-en.png"
alt="CANN" height="94"
border="0" width="94"></span>[icann.org]</a>
<br>
</p>
<h2>News Alert<br>
</h2>
<p
style="margin-right:0in;margin-bottom:7.5pt;margin-left:0in"><span
style="font-family:Arial"
class="font"><a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D05-2D03-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=6Eivc2vwZqN_e1JXuWLbbADqE8SwODCZpZh_nucxv68&e=">https://www.icann.org/news/ann<wbr>ouncement-2017-05-03-en[icann.<wbr>org]</a></span><br>
</p>
<div class="MsoNormal"
style="margin-top:15.0pt;text-align:center"
align="center">
<hr align="center" size="2"
width="100%"><br>
</div>
<h2
style="margin-bottom:0in;margin-bottom:.0001pt">Revised
ICANN Procedure for Handling Whois
Conflicts with Privacy Law:
Assessment and Next Steps Now
Available for Public Comment<br>
</h2>
<p
style="margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt">3
May 2017<br>
</p>
<p>LOS ANGELES – 3 May 2017 – The
Internet Corporation for Assigned
Names and Numbers (ICANN) today
published a paper, "Revised ICANN
Procedure for Handling Whois
Conflicts with Privacy Law:
Assessment and Next Steps," for
public comment.<br>
</p>
<p><b><a moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D03may17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=AFF2DPSvZ3TgeLC-8lrmCCBUTDPwPef3SVwBvlXW0KI&e=">Read
the Revised ICANN Procedure
for Handling Whois Conflicts
with Privacy Law: Assessment
and Next Steps[icann.org]</a></b>
[PDF, 159 KB].<br>
</p>
<p>This paper is available for
public comment through 12 June
2017. Feedback will be
incorporated into a report of
public comments and provided to
the Generic Names Supporting
Organization (GNSO) Council for
their review and consideration.<br>
</p>
<p><b><a moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_whois-2Dprivacy-2Dlaw-2D2017-2D05-2D03-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=q6EIeQotm2_QYjG4lebrrBkaHljOPA1SRCgXvOoCNVc&e=">Comment
on the Revised ICANN Procedure
for Handling Whois Conflicts
with Privacy Law: Assessment
and Next Steps[icann.org]</a></b>.<br>
</p>
<p>In accordance with the <a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D2008-2D01-2D17-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=JVtDVVlkiVKJlfNhAHNYjoWK5MSHkcxOLn9mfm2Hb64&e=">
ICANN Procedure for Handling
Whois Conflicts with Privacy Law
(Whois Procedure)[icann.org]</a>,
this paper opens a review process
to gather community input on the
effectiveness of the revised Whois
Procedure, which was made
effective on 18 April 2017.
Furthermore, as requested by the
GNSO Council, ICANN is publishing
this paper to provide analysis of
and solicit community input on the
practicality and feasibility of
the triggers, as well as
suggestions for moving forward
with the review. Outputs from this
assessment and comment process are
expected to inform the next
periodic review of the procedure.<br>
</p>
<p>The Whois Procedure has recently
been updated, although no
ICANN-accredited registrar or
registry operator to date has
formally invoked the procedure. As
a result, this analysis is based
solely on community discussions
and input received during the <a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_drafts_iag-2Dreview-2Dwhois-2Dconflicts-2Dprocedure-2D23may16-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=iA9BlMBg6D_w9aDcbBYK0tHeze09v7D_jlxJiE932k0&e=">
previous review[gnso.icann.org]</a>
[PDF, 155 KB], which related to
allowing for evaluation of an
additional trigger for invoking
the procedure. It also draws upon
ICANN's experience administering
other processes where a contracted
party is seeking ICANN's approval
for new services, or waiving
certain contractual requirements,
as a point of comparison for the
implementation of the procedure.<br>
</p>
<h3>About ICANN<br>
</h3>
<p><i>ICANN's mission is to help
ensure a stable, secure and
unified global Internet. To
reach another person on the
Internet, you have to type an
address into your computer - a
name or a number. That address
has to be unique so computers
know where to find each other.
ICANN helps coordinate and
support these unique identifiers
across the world. ICANN was
formed in 1998 as a
not-for-profit public-benefit
corporation and a community with
participants from all over the
world. ICANN and its community
help keep the Internet secure,
stable and interoperable. It
also promotes competition and
develops policy for the
top-level of the Internet's
naming system and facilitates
the use of other unique Internet
identifiers. For more
information please visit: <a
moz-do-not-send="true"
rel="noreferrer nofollow
noopener"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=FlLnWuWfHq02ox_3kxWHFf4D9p7Hlq8vaIH10JNTVvI&s=W1cz9M9nk_PfKsxr4Zt6P_5CLDlAKZTsgrAVo_569x8&e=">
www.icann.org[icann.org]</a>.</i><br>
</p>
</div>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"> <br>
</p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
<br>
</body>
</html>