<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Agreed. We should be extra careful to use this opportunity not just
to look at the questions we asked, but put the entire first report
to the test of the comments. If we did anything less, we would
ignore the essence of the comments. <br>
<br>
This includes the question of why an accreditation system is
preferrable to any other method of achieving those goals, btw.<br>
<br>
Best,<br>
<br>
Volker<br>
<br>
<br>
<div class="moz-cite-prefix">Am 15.07.2015 um 17:58 schrieb James M.
Bladel:<br>
</div>
<blockquote
cite="mid:D688F3A3-794E-41CC-8544-B221765B2FBF@godaddy.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>While I agree with previous commenters, I'd like to point out
that it isn't just the volume of comments received that will
require more time to review, but rather the substantive "holes"
or "gaps" identified during this process that we need to
address. Whether these had come from thousands of comments or
just a handful, I believe they will take more time to process. <br>
<br>
Thank you,
<div><br>
</div>
<div>J.</div>
<div>____________</div>
<div>James Bladel</div>
<div>GoDaddy</div>
</div>
<div><br>
On Jul 15, 2015, at 10:28, Carlton Samuels <<a
moz-do-not-send="true" href="mailto:carlton.samuels@gmail.com">carlton.samuels@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:large">
+1. </div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:large">
<br>
</div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:large">
Kathy's arguments offered in favour of more time to
usefully treat the comments are impatient of debate.</div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:large">
<br>
</div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:large">
-Carlton</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: 876-818-1799<br>
<i><font color="#33CC00">Strategy, Planning, Governance,
Assessment & Turnaround</font></i><br>
=============================</div>
</div>
<br>
<div class="gmail_quote">On Wed, Jul 15, 2015 at 10:20 AM,
Kathy Kleiman <span dir="ltr">
<<a moz-do-not-send="true"
href="mailto:kathy@kathykleiman.com" target="_blank">kathy@kathykleiman.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Hi All, I posted
this email earlier today, but have not seen it pop up
the list. Resending...<br>
Best,<br>
Kathy<br>
<div>----------------------------------------------------------------------------------------------------------------------------------------------------<br>
All,<br>
I agree with the emails of Volker and James G. that
we have to do a thorough review of the comments. I
also agree with the expansion of the time frame to
do it.
<br>
<br>
The last time we had such an outpouring of comments
at ICANN that I can remember was the Closed Generic
proceeding and comments to the Board. Dozens of
comments flowed in from parties who do not
traditionally participate in ICANN processes. The
Board took the time to read, evaluate and respond to
the comments.<br>
<br>
Here too we must take the time to read, evaluate and
respond to the comments. As Volker points out, the
issues before us are not only the questions we
issued, but the consensus we presented. Do others
agree with our consensus? Do they support our
direction? Would they push it more in one direction
or another or reject it outright? <br>
<br>
One thing I have seen in my skimming of the comments
is a lot of discussion of Due Process. There appears
to be a good amount of commentary on this issue, and
one we will need to read and evaluate closely.
<br>
<br>
Over the year of our work we have talked often about
the month of August. How it is a time that many in
certain countries take long vacations; how emails to
business addresses are often unanswered until the
person returns to her/his desk. I think a rush on
this in the dead of summer is a) unnecessary b) will
not result in full staffing of the teams that we are
setting up and c) will not give us the time for the
evaluation, analysis and incorporation that we need.<br>
<br>
Analysis, evaluation, incorporation -- this is a
very important task for us now. <br>
Best,<br>
Kathy<br>
<br>
<br>
<br>
<div>On 7/15/2015 5:50 AM, Volker Greimann wrote:<br>
</div>
<blockquote type="cite">Hi all,<br>
<br>
considering the outpouring of comments, we should
not limit ourselves to these three topics but
rather try to see how the comments affect the
entire work so far. It does make sense to check
the comments for these issues, but not
exclusively.
<br>
<br>
That said, I volunteer for the first team.<br>
<br>
I support the sugestion to "collapse" yes and no
responses.<br>
<br>
Best,<br>
<br>
Volker<br>
<br>
<div>Am 15.07.2015 um 00:50 schrieb Mary Wong:<br>
</div>
<blockquote type="cite">
<div>Dear WG members,</div>
<div><br>
</div>
<div>Following from the WG call earlier today,
the co-chairs and staff after some
consultation would like to propose the
following approach for your consideration:</div>
<div><br>
</div>
<div><u>1. Use of Sub Teams for Specific Topics</u>:</div>
<ul>
<li>Sub-teams comprising a few WG volunteers
each can be formed to do the initial review
of public comments received on the three
topics suggested by Steve on the call, i.e.
(1) Section 1.3.2 of the Initial Report (on
escalation of relay requests and the
handling of disclosure/publication requests
from third parties other than IP rights
holders); (2) Section 1.3.3 (on the open
question regarding online financial
transactions); and (3) Annex E (the
Illustrative Disclosure Framework).
</li>
<li>To assist the WG evaluate the usefulness
of sub teams, a sub team for Section 1.3.2
can be formed first and serve as a “test
case” for the exercise.
</li>
<li>As outlined on the call, a sub team will
do a “first pass” through a template, based
on the Public Comment Review Tool, that
staff will populate with all the input
received on that particular issue. The sub
team will report back to the full WG in a
timely fashion, including suggesting a WG
response and/or proposed action in relation
to the comments received.
</li>
<li>Sub teams may elect to do their work via
email and online tools (e.g. Google Docs or
a wiki page), with or without supplemental
conference calls. Any calls will be recorded
and transcribed for transparency purposes,
and drafts and other documents prepared
using online tools will also be made
available to the full WG. (Do note, however,
that depending on call scheduling and
timing, staff support may not be available
for all requested calls if several sub teams
are used concurrently.)
</li>
</ul>
<div><b>PLEASE VOLUNTEER FOR SUB TEAM 1.3.2 IF
YOU ARE INTERESTED IN ASSISTING WITH THIS
INITIAL REVIEW.
</b>Staff will endeavor to provide the
template tool for 1.3.2 to the sub team as
soon as possible, hopefully by Monday.</div>
<div><br>
</div>
<div><u>2. Full WG Review of Other Comments to
Continue in Parallel</u>:</div>
<ul>
<li>Staff will “collapse” (per James’
suggestion on the call) all those template
responses received that were simply a Yes or
No answer to a question, without any further
comment added – these will be reflected in
the Public Comment Review Tool accordingly,
as a single collective entry. The current
Tool (covering Preliminary Recommendations 1
through 9) will be updated in time for the
WG to begin this review on the next call.
</li>
</ul>
<div><br>
</div>
<div><u>3. Collated Information</u>:</div>
<ul>
<li>In addition to the updated spreadsheet
just circulated by Graeme, we can also send
you archived mail files of the contributions
received to the public comment forum, should
you or your group wish to conduct searches
through each comment yourselves.
</li>
</ul>
<div><br>
</div>
<div>We hope the above will be helpful in
facilitating good progress on the work to be
done in preparation for the Final Report.</div>
<div><br>
</div>
<div>Thanks and cheers</div>
<div>Mary</div>
<div><br>
</div>
<div>
<div>
<div><font color="#000000"><font
face="Calibri">Mary Wong</font></font></div>
<div><font color="#000000"><font
face="Calibri">Senior Policy Director</font></font></div>
<div><font color="#000000"><font
face="Calibri">Internet Corporation
for Assigned Names & Numbers
(ICANN)</font></font></div>
<div><font color="#000000"><font
face="Calibri">Telephone: <a
moz-do-not-send="true"
href="tel:%2B1%20603%20574%204889"
value="+16035744889" target="_blank">
+1 603 574 4889</a></font></font></div>
<div><font color="#000000"><font
face="Calibri">Email: <a
moz-do-not-send="true"
href="mailto:mary.wong@icann.org"
target="_blank">
mary.wong@icann.org</a></font></font></div>
<div><br>
</div>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
<div>
<div><br>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a moz-do-not-send="true" href="mailto:Gnso-ppsai-pdp-wg@icann.org" target="_blank">Gnso-ppsai-pdp-wg@icann.org</a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
<pre cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: <a moz-do-not-send="true" href="tel:%2B49%20%280%29%206894%20-%209396%20901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a moz-do-not-send="true" href="tel:%2B49%20%280%29%206894%20-%209396%20851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a moz-do-not-send="true" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a moz-do-not-send="true" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a moz-do-not-send="true" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a moz-do-not-send="true" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a moz-do-not-send="true" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a moz-do-not-send="true" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a moz-do-not-send="true" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: <a moz-do-not-send="true" href="tel:%2B49%20%280%29%206894%20-%209396%20901" value="+4968949396901" target="_blank">+49 (0) 6894 - 9396 901</a>
Fax.: <a moz-do-not-send="true" href="tel:%2B49%20%280%29%206894%20-%209396%20851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a moz-do-not-send="true" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a moz-do-not-send="true" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a moz-do-not-send="true" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a moz-do-not-send="true" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a moz-do-not-send="true" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a moz-do-not-send="true" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a moz-do-not-send="true" href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a moz-do-not-send="true" href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a moz-do-not-send="true" href="mailto:Gnso-ppsai-pdp-wg@icann.org" target="_blank">Gnso-ppsai-pdp-wg@icann.org</a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
<br>
</div>
<br>
</div>
<br>
_______________________________________________<br>
Gnso-ppsai-pdp-wg mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg"
rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Gnso-ppsai-pdp-wg mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a></span><br>
<span><a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></span></div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>