<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I too unfortunately missed that call, and as I indicated previously, I don't find this fair. It presumes guilt on the part of proxy customers.<div>Stephanie P<br><div><div>On 2014-04-14, at 9:52 AM, Volker Greimann wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<div text="#000000" bgcolor="#FFFFFF">
Hi Steve,<br>
<br>
as I missed that call, was that number of members in any way
qualified or multi-stakeholder or was it just a voice from a certain
part of the community. If so, any comment to that effect (if it were
to be included) should also include the origin of that opinion.<br>
<br>
Volker<br>
<br>
<div class="moz-cite-prefix">Am 14.04.2014 15:45, schrieb Metalitz,
Steven:<br>
</div>
<blockquote cite="mid:E5B4A2ED43DFAE4F9E710FA54FEF8F622959C452@LAEX02.MSK.local" type="cite">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:"?? ??";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Cambria","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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Cambria","serif";}
@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:814294924;
mso-list-template-ids:-1228908920;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
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:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">Hi
Marika,
<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><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
believe that at the beginning of the April 8 call there was
discussion about including in the preliminary conclusion on
Question B-2 the view of a number of members of the WG that
the minimum verification or validation standards for
accredited services would need to exceed those applicable to
non-proxy registrations, but that this view could be
affected by the outcome of discussions regarding relay and
reveal requirements (e.g., re the speed of reveal). It does
not appear that the template for question B-2 has been
supplemented to reflect this discussion. Could staff please
do so? Thanks.
<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><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Steve
Metalitz<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>
<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-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Marika Konings<br>
<b>Sent:</b> Thursday, April 10, 2014 4:45 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg] For your review -
revised template Category B - question 3<o:p></o:p></span></p>
</div>
</div><p class="MsoNormal"><o:p> </o:p></p>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Dear
All,<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Following
our call on Tuesday, please find attached the updated
template for Cat B – Q 3 which aims to capture the main
points of discussion as well as a proposed preliminary
conclusion based on the deliberations to date ('</span><span style="font-family:"Times New
Roman","serif"">The WG recommends that any
rights, responsibilities and obligations for registrants
as well as privacy/proxy providers would need to be
clearly communicated in the registration agreement,
including any specific requirements applying to transfers
and renewals. However, further details as to what minimum
requirements for such rights, responsibilities and
obligations may be will need to be further discussed by
the WG following its review of other charter questions').
If I've missed anything or you have any proposed edits,
feel free to share your suggestions with the mailing list.<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">As
noted during the call, further input and discussion will
be required in relation to the second part of the charter
question: clarify how transfers, renewals, and PEDNR
policies should apply? Below you will find our initial
attempt to identify some of the questions that may need to
be addressed in this regard. We hope that WG members, and
especially registrars, will be able to add to this list
and/or provide some initial thoughts and suggestions.
We'll kick off the meeting next week with a short
introduction to the Inter-Registrar Transfer Policy
(IRTP), but in the meantime you may already want to review
this presentation that was provided by James Bladel for
one of the IRTP WGs (<a moz-do-not-send="true" href="http://gnso.icann.org/en/meetings/presentation-irtp-c-training-29nov11-en.pdf"><span style="background:white">Powerpoint</span></a><span style="background:white">, </span><a moz-do-not-send="true" href="http://gnso.icann.org/meetings/transcript-irtp-c-training-29nov11-en.pdf"><span style="background:white">Transcript</span></a><span style="background:white"> and </span></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:blue"><a moz-do-not-send="true" href="http://audio.icann.org/gnso/gnso-irtp-c-training-20111129-en.mp3"><span style="background:white">MP3-Recording</span></a></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">).<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Best
regards,<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Marika<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><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:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Marika
Konings <<a moz-do-not-send="true" href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>><br>
<b>Date: </b>Monday 17 March 2014 12:40<br>
<b>To: </b>"<a moz-do-not-send="true" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>"
<<a moz-do-not-send="true" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br>
<b>Subject: </b>[Gnso-ppsai-pdp-wg] For your review -
template Category B - question 3<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Dear
All,<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">In
preparation for our meeting tomorrow, please find
attached the proposed template for Category B –
question 3 (<i>What rights and responsibilities should
domain name registrants that use privacy/proxy
services have? What obligations should
ICANN-accredited privacy/proxy service providers
have in managing these rights and responsibilities?
Clarify how transfers, renewals, and PEDNR policies
should apply.)
</i>If there is any additional information that should
be added to the background section, please let me
know.<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">In
relation to transfers, renewals and PEDNR policies,
we've started to develop a list of questions that the
WG may need to consider in relation to these policies.
If there are any additional questions that should be
included, please feel free to suggest. We are hoping
that some of the registrar members will be able to
shed a light on how these issues are currently handled
and whether or not these need to be factored into the
WG recommendations.<o:p></o:p></span></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Per
the ERRP, 'registrars must notify the registered
name holder of the expiration at least two times'.
Should there be a requirement for the P/P provider
to pass these notices on to the P/P customer? <o:p></o:p></span></li>
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Per
the ERRP, 'if a registration is not renewed by the
RAE or deleted by the registrar, within five days
after the expiration of the registration, the
registrar must transmit at least one additional
expiration notice to the RAE that includes
instructions for renewing the registration'. Should
there be a requirement for the P/P provider to pass
these notices on to the P/P customer?<o:p></o:p></span></li>
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Per
the ERRP, 'beginning at the time of expiration and
through the DNS resolution interruption period
described in paragraphs 2.2.2 and 2.2.3, the RAE
must be permitted by the registrar to renew the
expired registration'. What if the underlying
customer wants to renew the registration? Idem for
restoration during the Redemption Grace Period.<o:p></o:p></span></li>
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">In
relation to the IRTP, should there be any
restrictions concerning transfers of P/P
registrations? (e.g. some of the terms and
conditions require the P/P services to be removed
during the transfer process). Depending on the
response to this question, all communications in the
IRTP currently go via the transfer contact
(Registered Name Holder / Admin Contact). Should
there be any requirements for this information to
also be communicated to the P/P customer? What
happens if there is a disagreement relating to the
transfer between the P/P provider and the P/P
customer?<o:p></o:p></span></li>
</ul>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Best
regards,<o:p></o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div><p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Marika<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<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>
</div>
_______________________________________________<br>Gnso-ppsai-pdp-wg mailing list<br><a href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><br>https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</blockquote></div><br></div></body></html>