<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I feel that we should at least wait until Dublin before we slam the
door shut on further review. With the day we have for our face to
face, a lot can be achieved and I feel we would be doing our work a
disservice by robbing ourselves of this opportunity.<br>
<br>
Volker<br>
<br>
<div class="moz-cite-prefix">Am 21.08.2015 um 02:36 schrieb Mary
Wong:<br>
</div>
<blockquote cite="mid:D1FBE54E.1726A%25mary.wong@icann.org"
type="cite">
<div>
<div>Hi Stephanie and everyone,</div>
<div><br>
</div>
<div>The deadline was set to try to identify for the WG as many
issues possibly meriting further WG consideration as we can.
This will help the co-chairs plan the agendas for the coming
weeks, including looking ahead to the Dublin meeting, and see
how well we are able to keep to the Work Plan. As noted by
Steve on the last call, the current Work Plan timeline has
actually be extended since the WG issued its Initial Report in
early May – once to allow for an extended public comment
period as requested by some WG members, and then again
subsequently in view of the number of comments that came in.</div>
<div>
<div><br>
</div>
</div>
</div>
<div>While we are very cognizant of the amount of work it will
take to complete a review of the comments, do note that our WG
is operating under the “external” constraint that is the January
2017 expiration date of the current interim P/P specification in
the RAA. Note also that even in the best case scenario under our
current Work Plan, if the WG completes its Final Report in time
for the GNSO Council’s November meeting, the following still has
to happen:</div>
<ul>
<li>Council votes to adopt the WG’s consensus recommendations;</li>
<li>Recommendations Report prepared for Council approval;</li>
<li>Report sent to the ICANN Board and publication of
recommended actions by ICANN Board (i.e. adoption of the
policy) published for public comment;</li>
<li>Review and vote by the ICANN Board;</li>
<li>Formation of an Implementation Review Team and development
of an Implementation Plan</li>
<li>Finalization of operational details and announcement of
launch date of accreditation program – note that GDD and the
contracted parties aim for this to be six months prior to the
actual effective date.</li>
</ul>
<div>As you can see from the above, the current timeline already
leaves very little time to take the policy from adoption to
implementation, and any further extension brings both the WG and
the eventual IRT up even closer against the January 2017
deadline. Given the momentum that the Sub Teams seem to be
developing on the tricky open questions, the idea was that the
rest of the WG could concurrently begin to close on final
recommendations for the preliminary recommendations. </div>
<div><br>
</div>
<div>Perhaps it will also help to note that what is required at
this stage is for the WG to consider what (if anything) needs to
be changed, deleted, or added to in terms of the preliminary
recommendations. The Work Plan envisages about 2-3 weeks
following the Sub Teams’ final reports for further WG discussion
of the issues identified now for that purpose, so that by Dublin
we will be able to focus on finalizing any remaining open or
contentious topics.</div>
<div><br>
</div>
<div>I’m of course not saying that the Work Plan cannot be changed
if the co-chairs and WG members believe that to be the most
appropriate thing to do, but I hope that this email setting out
the context for our work is helpful in some way.</div>
<div><br>
</div>
<div>Cheers</div>
<div>Mary</div>
<div><br>
</div>
<div>
<div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Mary Wong</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Senior Policy
Director</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Internet
Corporation for Assigned Names & Numbers (ICANN)</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Telephone: +1
603 574 4889</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Email:
<a class="moz-txt-link-abbreviated" href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></font></font></div>
<div><br>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span
style="font-weight:bold">From: </span> <<a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a></a>>
on behalf of Stephanie Perrin <<a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>><br>
<span style="font-weight:bold">Date: </span> Thursday, August
20, 2015 at 15:26<br>
<span style="font-weight:bold">To: </span> "<a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a></a>"
<<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span> Re:
[Gnso-ppsai-pdp-wg] Last call for Issue-Spotting on Part 2
plus New Comments to Review (Parts 3 & 4)<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
0 0 5;">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div bgcolor="#FFFFFF" text="#000000">
What happens if we find something after the deadline,
Mary? I appreciate the desire to push this thing on but I
reiterate that some of us have other lives and family
holidays during this period, and I think the work effort
required to go through all these comments demands more
time. I will keep saying this, I am trying to throw my
boots off the toboggan and slow us down so that we can do
a thorough job on this....the kind of job that 22000
comments deserves.<br>
Sorry if that seems not being constructive to some, but it
seems only fair to me. I am sure I am not the only one
who has not been through all the comments.
<br>
kind regards <br>
Stephanie Perrin<br>
<br>
<div class="moz-cite-prefix">On 2015-08-20 12:50, Mary
Wong wrote:<br>
</div>
<blockquote
cite="mid:D1FB7D72.17247%25mary.wong@icann.org"
type="cite">
<div>Dear WG members,</div>
<div><br>
</div>
<div>This is a <u>last call</u> for any issues that you
would like to bring to the WG’s attention concerning
Part 2 of the WG Public Comment Review Tool (first
circulated on 10 August), similar to the approach we
adopted for issue-spotting in Part 1. Please send
these to the email list for consideration at the next
WG call as soon as you can, but
<b>no later than Monday</b> (a day before the call) if
at all possible. </div>
<div><br>
</div>
<div>Please also find attached two documents - </div>
<div><br>
</div>
<div>(1) Part 3 of the WG Public Comment Review Tool,
containing excerpts from public comments sent directly
to the public comment forum and responses to the
online questions template that cover all the WG's
remaining preliminary recommendations aside from those
being analyzed by the Sub Teams (i.e. Preliminary
Recommendations #16-20); and</div>
<div><br>
</div>
<div>(2) Part 4 of the WG Public Comment Review Tool,
containing those comments and suggestions made by
commenters and template responders that were not
specifically framed as responses to particular WG
recommendations. Part 4 also contains two additional
elements, viz. a list of the types of concerns raised
by signatories to the Save Domain Privacy petition
(much of which is also reflected in many of the
general comments received in the public comment
forum), and a list of commenters who supported or
endorsed other commenters’ submissions. While this
Part 4 may be of particular usefulness to Sub Team 4,
we attach it here to facilitate the WG's review of all
the remaining comments not otherwise summarized in
other parts of the Tool.</div>
<div><br>
</div>
<div>These two documents are the last in the series of
documents that comprise the WG’s Public Comment Review
Tool for our Initial Report, not including the
additional documents that were prepared for the
various Sub Teams that will also form part of the
record for the Final Report. I should point out that
some of the comments in these two documents include
some strong language, but we have chosen to leave them
in as they were sent in the same way as comments that
used less robust language; I hope that is all right. </div>
<div><br>
</div>
<div>Cheers</div>
<div>Mary</div>
<div><br>
</div>
<div>
<div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Mary
Wong</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Senior
Policy Director</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Internet
Corporation for Assigned Names & Numbers
(ICANN)</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Telephone:
+1 603 574 4889</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font
class="Apple-style-span" face="Calibri">Email:
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></font></font></div>
<div><br>
</div>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div><br>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><a moz-do-not-send="true" 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>
</div>
</div>
</blockquote>
</span>
<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>