<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Actually, and I do hate to belabor this but:<br>
1. I thought you were proposing to drop the entire proposed new
section and merely footnote the disagreement. I like that option a
lot.<br>
2. If we are proposing to keep the text, then there should be a
balanced construction. I include once again the preamble, which
affects that balance:<br>
<br>
<i>Although the WG agreed that the mere fact that a domain name is
registered by a commercial entity or by anyone conducting
commercial activity should not preclude the use of P/P services ,
there was disagreement over whether domain names that are actively
used for commercial transactions (e.g. the sale or exchange of
goods or services) should be prohibited from using P/P services.
While most WG members did not believe such a prohibition is
necessary or practical, some members believed that registrants of
such domain names should not be able to use or continue using
proxy or privacy services.
</i><i><br>
</i><i>
</i><i><br>
</i><i>For those that argued that it is necessary and practical to
limit access to P/P services to exclude commercial entities, the
following text was proposed to clarify and define their position:
"domains used for online financial transactions for commercial
purpose should be ineligible for privacy and proxy registrations."
</i><i><br>
</i><i><b>For those that argued that limiting access to P/P services
to exclude entities who were engaged in online financial
transactions was impracticable and created an unacceptable risk
to NGOs and vulnerable organizations who had legitimate needs
for the services</b></i><i>, the following text was proposed to
clarify and define their position: "Attempting to distinguish the
end purposes of a domain registration is not practicable for the
purposes of determining eligibility for privacy/proxy services,
and may unfairly discriminate against vulnerable groups and
organizations who wish to exercise their rights of free speech on
the Internet".</i><i><br>
</i><i>
</i><i><br>
</i><i>Public comment is therefore specifically invited on the
following questions:
</i><i><br>
</i><i>
</i><i><br>
</i>
<ul>
<li><big><big><big><big><big><span style="font-size: 11pt;
line-height: 150%; font-family: Calibri,
sans-serif;" lang="EN-GB">Should registrants of
domain names associated with commercial activities
and which are used for online financial transactions
be prohibited from using, or continuing to use,
privacy and proxy services? If so, why, and if not,
why not?</span><o:p></o:p></big></big></big></big></big></li>
</ul>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"><big><big><big><big><big><span style="font-size:
11pt; line-height: 150%; font-family: Calibri,
sans-serif;" lang="EN-GB">If [so, will] <b>you
agree with this position, do you think it would</b>
be useful to adopt a definition of “commercial” or
“transactional” to define those domains for which
P/P service registrations should be disallowed? And
if so, what should the definition(s) be?”</span><o:p></o:p>
</big></big></big></big></big></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3"><big><big><big><big><big><span style="font-size:
11pt; line-height: 150%; font-family: Calibri,
sans-serif;" lang="EN-GB">{Will} <b>Would </b>it
be necessary to make a distinction in the WHOIS data
fields to be displayed as a result? (this question
is not clear, in my view, it needs more detail on
the nature of the distinction, the data fields we
are talking about, and to what does "as a result"
refer? As a result of the decision to deny privacy
proxy services???)</span></big></big></big></big></big></li>
</ul>
<i><br>
</i>
<blockquote><i><b>* What risks do you foresee with either option?</b></i><br>
</blockquote>
<br>
I would note that the clarifying questions here go to proposing
draft text for the report, right down to the definition and data
fields. I have added a question on risk....because before coming up
with draft text to implement the banning of P/P use by those engaged
in commercial activity (via the comments in response to this
invitation), we have to look at the many risks here....key among
them being that privacy proxy services will be priced out of the
market by the complexity of the exercise, a point that registrars
made on a number of occasions. This is an excellent outcome for
those who do not favor them, but the NCSG certainly considers the
services to be essential (I can only speak for them, but I know
there is support in other quarters).<br>
Further, the final question is neutral, as there are clearly risks
on both sides, and we seek the answers for both.<br>
<br>
Cheers SP<br>
<br>
---
<br>
<div class="moz-cite-prefix">On 2015-05-01 1:06, Graeme Bunton
wrote:<br>
</div>
<blockquote cite="mid:5542531F.5050804@tucows.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Good suggestions, Steve. <br>
Thank you,<br>
Graeme<br>
<br>
<div class="moz-cite-prefix">On 2015-04-30 11:58 AM, Metalitz,
Steven wrote:<br>
</div>
<blockquote
cite="mid:E5B4A2ED43DFAE4F9E710FA54FEF8F6229BCEC19@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: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:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:Garamond;
        panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
        {font-family:"Times New Roman \, serif";
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        line-height:150%;
        font-size:12.0pt;
        font-family:"Garamond","serif";
        color:black;
        mso-fareast-language:AR-SA;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        line-height:150%;
        font-size:12.0pt;
        font-family:"Garamond","serif";
        color:black;
        mso-fareast-language:AR-SA;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        line-height:normal;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;
        mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        line-height:150%;
        font-size:12.0pt;
        font-family:"Garamond","serif";
        color:black;
        mso-fareast-language:AR-SA;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;
        mso-fareast-language:AR-SA;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle23
        {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;}
/* List Definitions */
@list l0
        {mso-list-id:453985781;
        mso-list-template-ids:580653038;}
@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;}
@list l1
        {mso-list-id:683018229;
        mso-list-template-ids:87975168;}
@list l1: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 l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2
        {mso-list-id:1484351411;
        mso-list-template-ids:182245810;}
@list l2: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 l2:level2
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l2:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3
        {mso-list-id:1760366182;
        mso-list-template-ids:914520856;}
@list l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">Perhaps
a simpler way to accomplish this would be to insert the
following at the end of the first bullet:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">“If
so, why, and if not, why not?”<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">We
could then introduce the next two questions with “If so,”
and change “will” to “would” as Stephanie suggests.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;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" style="line-height:normal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-US">
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
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>Stephanie Perrin<br>
<b>Sent:</b> Thursday, April 30, 2015 11:23 AM<br>
<b>To:</b> <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>;
Mary Wong<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] PPSAI Comment
Period and Section 1.3.3<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thanks Mary,
very helpful. Returning to the original text, I offer the
following suggestions:<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span
style="font-family:"Calibri","sans-serif""
lang="EN-GB">For those that argued that it is necessary
and practical to limit access to P/P services to exclude
commercial entities, the following text was proposed to
clarify and define their position: “domains used for
online financial transactions for commercial purpose
should be ineligible for privacy and proxy registrations.”<br>
<br>
Public comment is therefore specifically invited on the
following questions: </span> <o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo1"> <span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif""
lang="EN-GB">Should registrants of domain names
associated with commercial activities and which are used
for online financial transactions be prohibited from
using, or continuing to use, privacy and proxy services?
</span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo1"> <span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif""
lang="EN-GB">If [so, will] <b>you agree with this
position, do you think it would</b> be useful to
adopt a definition of “commercial” or “transactional” to
define those domains for which P/P service registrations
should be disallowed? And if so, what should the
definition(s) be?”</span><span lang="EN-GB"> </span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo1"> <span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif""
lang="EN-GB">{Will} <b>Would </b>it be necessary to
make a distinction in the WHOIS data fields to be
displayed as a result? (this question is not clear, in
my view, it needs more detail on the nature of the
distinction, the data fields we are talking about, and
to what does "as a result" refer? As a result of the
decision to deny privacy proxy services???)</span><o:p></o:p></li>
</ul>
<p class="MsoNormal">The use of the word "will" here appears
to imply agreement with the text, you need the conditional.
Then you need to seek clarification on the other side:<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo2"> If you disagree with the proposal to deny
the use of privacy and proxy services to domain names
associated with commercial activities and which are used
for online financial transactions, what are the reasons
for your rejection of this proposal?<o:p></o:p></li>
</ul>
<p class="MsoNormal"><br>
Kind regards as always, <br>
Stephanie Perrin<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2015-04-30 22:54, Mary Wong wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">To add to Stephanie’s note that
this specific issue - whether registrants of domain
names actively used for commercial transactions
ought to be disallowed from using P/P services - had
been discussed at some length by the WG:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please note that this part of the
Initial Report draws heavily on the detailed WG
template for Charter Category C that was the basis
for the WG’s deliberations on this topic. That
template contains lengthy descriptions of what had
previously been termed the majority and minority
positions on the WG’s answer to this specific issue.
As part of the WG’s deliberations – which took place
primarily between April and June 2014 - the more
specific formulation of “transactional” to describe
the sort of commercial (i.e. Involving financial
transactions) activities that were being discussed
was included in the language. All the templates and
suggested formulations discussed by the WG are
recorded and published on the WG wiki.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The WG ultimately agreed to
retain the two positions in the Initial Report and
to revisit the question during its review of the
public comments received. As noted previously, the
WG's views were presented to the community in London
in June 2014 and again in Los Angeles in October
2014.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Therefore, the three questions in
Section 1.3.3 of the Executive Summary <u>only</u>
go toward soliciting community input on this single
issue. They were not intended to represent a view of
any “side” in the WG with regard to this matter. If
the WG prefers, we can add a sentence to clarify and
specify the reason for the questions in Section
1.3.3. Fundamentally, the idea is that public
comments will facilitate the WG’s eventual
resolution of this issue as part of its preparation
of the Final Report. <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We hope this reminder of the
background is of assistance.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Mary<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif"">Mary
Wong</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif"">Senior
Policy Director</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif"">Internet
Corporation for Assigned Names & Numbers
(ICANN)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif"">Telephone:
+1 603 574 4892</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Calibri","sans-serif"">Email:
<a moz-do-not-send="true"
href="mailto:mary.wong@icann.org">
mary.wong@icann.org</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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;line-height:150%;font-family:"Calibri","sans-serif"">From:
</span></b><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif"">Stephanie
Perrin <<a moz-do-not-send="true"
href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>><br>
<b>Date: </b>Thursday, April 30, 2015 at 09:20<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>>,
James Gannon <<a moz-do-not-send="true"
href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</a>>,
Michele Blacknight <<a moz-do-not-send="true"
href="mailto:michele@blacknight.com">michele@blacknight.com</a>><br>
<b>Subject: </b>Re: [Gnso-ppsai-pdp-wg] PPSAI Comment
Period and Section 1.3.3<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times
New Roman","serif""><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF
4.5pt;padding:0in 0in 0in
4.0pt;margin-left:3.75pt;margin-right:0in"
id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<p class="MsoNormal">James, prior to you joining the
group, we had discussed this at some length. IN
fact, I really thought that the many reasons why
sorting out the purpose of a registration is
problematic had buried this debate, but apparently
not. Some of the issues raised, according to my
recollection were the following:<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> names are registered prior to
decisions about content <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> content changes over time <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> most countries regulate e-commerce
in some fashion, so that website commercial
activity does not have to be regulated by ICANN <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> ICANN should not be in the business
of regulating content in the first place (and
sorting out who is extracting a material
consideration from a website in order to deny them
the ability to use a proxy registration is
certainly a form of regulation) <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> definitions of commercial activity
vary widely around the world<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> bad actors will not declare,
registrars cannot police this matter <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> criminal prosecution is not
dependent on WHOIS information <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> if this is really about the ability
to detect market information, ICANN should not be
in the business of making registrant information
available for market purposes, it does it for
security and stability. <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l3
level1 lfo3"> contactability remains, regardless
of which registrant info appears in WHOIS <o:p> </o:p></li>
</ul>
<p>I am planning to reformulate these into questions
to match the questions on the other side,
suggestions welcome. <o:p></o:p></p>
<p class="MsoNormal">Stephanie Perrin<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2015-04-30 16:24, James
Gannon wrote:<o:p></o:p></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">I
don’t see this as asking providers to enforce
anything similar to other questions when
registering a domain, it’s a self-reported
assessment. All it does is add an additional
branch to the decision tree for eligibility,
which will already be there to determine
eligibility due to the other reasons listed
below.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">The
registrant is asked will you be processing
financial transactions. </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoListParagraph"
style="text-indent:-.25in"><span
style="font-size:11.0pt;line-height:150%;color:#1F497D">·</span><span
style="font-size:7.0pt;line-height:150%;font-family:"Times
New Roman","serif";color:#1F497D">
</span><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif"">Yes</span><span
style="font-family:Wingdings;mso-fareast-language:EN-US">à</span><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif"">Will
you be using a 3<sup>rd</sup> party>No>Not
eligible for P/P. </span><o:p></o:p></p>
<p class="MsoListParagraph"
style="text-indent:-.25in"><span
style="font-size:11.0pt;line-height:150%;color:#1F497D">·</span><span
style="font-size:7.0pt;line-height:150%;font-family:"Times
New Roman","serif";color:#1F497D">
</span><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif"">Yes</span><span
style="font-family:Wingdings;mso-fareast-language:EN-US">à</span><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif"">Will
you be using a 3<sup>rd</sup>
party>Yes>Eligible for P/P.</span><o:p></o:p></p>
<p class="MsoListParagraph"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">I’m
not asking registrars to enforce law but to see
if a more finely grained eligibility process can
be enacted. Or at least is there is public
support for more granularity.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">-James</span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="line-height:normal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">
Michele Neylon - Blacknight [<a
moz-do-not-send="true"
href="mailto:michele@blacknight.com">mailto:michele@blacknight.com</a>]
<br>
<b>Sent:</b> Thursday, April 30, 2015 8:17
AM<br>
<b>To:</b> James Gannon; Graeme Bunton;
PPSAI<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg]
PPSAI Comment Period and Section 1.3.3</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">James</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">As
a registrar or PP service provider how am I
meant to assess this?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">It
doesn’t scale</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Seriously.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">If,
for example, there is an Irish operated
website that is not complying with Irish law
then it would be up to the ODCE (<a
moz-do-not-send="true"
href="https://protect-us.mimecast.com/r/IqfLPS2xhmx-5GDCPCM4mLmlw-jOPQHGmhpzAjWDKActStEmX7ndjfqnEIgUMkdhXCAGe_aALVo69T0irIiCOftGW0RRkFeeJXP_SQ_bxxN5c9ZWrJzjnfSpDUeI4UjuT2dsrtgXox-JsiUyGsBvbDhSHcf2gH3gqSI2YwvUnORJuOhanPP2uCSQp3bey2BqQKbirhovyP6hDiunUi2Ilg">http://www.odce.ie/</a>) to
enforce whatever needs enforcing, as it
would be up to the DPA to enforce any issues
around data privacy etc., etc.,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Attempting
to force registrars and PP providers to make
these kind of evaluations is not going to
work.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Issues
like PCI-DSS compliance are matters that
should be dealt with by the DPA and the
banks.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Forcing
registrars and PP providers to start getting
involved in that kind of assessment isn’t
viable</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Regards</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Michele</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE">
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">--</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Mr
Michele Neylon</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Blacknight
Solutions</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Hosting,
Colocation & Domains</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true"
href="https://protect-us.mimecast.com/r/r0QiXaZk72F7OmWKc9_pO3HAiIAvI3h06-RcgETJh-J4kMLvQtMGZn5lKnoQO8ikZnQiTNL6FLbYD67s4dF-tWj2IbgtPVbZIrmLhFiT8cZvRoXUKLem6cyG8n3JE6-tis8tEkBPwKkOuqFU7azbPzFSZPBE0XjNt1o6W5MAy5yWOEr-3QLGcTYMC5oDDDwuftYuz9pHDOyvEieReE36N1UxTeWXBI__3g1_xmHN4S0">http://www.blacknight.host/</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true"
href="https://protect-us.mimecast.com/r/wl1MfvJ8aWTxnqz6FCsjG4QE5Lt8k3OKgMWheA8wVhCgpAj6NRi9Y8zMxa9MvTN2vhD-EWNpvAhObo3t9Jl-Kh7ki557bXwOMPGhz-Up4X8e1Q8UR-DF0d4jYhrGpb0LrotD50UduC3QQRYUJ24nEnbyayh-GPs3hk77LhEpDwYrSf4v_RqmohacWFuO-pMc6Ap8I9JulleUf0h9FbW-MHMc1xlq8F7WXPVnekaa_Tg">http://blog.blacknight.com/</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true"
href="https://protect-us.mimecast.com/r/-MRGGedz53TF8UWq3rKo8GI39ai_ismqN0UYggzFnhsCzIT83jwX24BSxN_VMtJYpUgkSGF-Qst71LuBVQLY87bs-vewJiEDX8p5ABHKofJc69pmthPRFaowH9cz7b4wBdr45nD9yW3n5wmmAGAorNORPO2oD8fx1b7Ch4UucRtocG7TVoD8q8xePkXjqmELFjL3powas7Q8SOSYQE947lLpZzCcGrOwqu7wogrVuvk">http://www.blacknight.press</a>
- get our latest news & media
coverage</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""><a
moz-do-not-send="true"
href="https://protect-us.mimecast.com/r/suwZNIiJfrdSpqE4iC56mMY3x3S91aHmdyA2bCRS-Fmr9Q1_uNxFISl4UXNQGJAa4ABDSoMKKJoH4LBI6dPDpw1IcPIW2UD6KmY-khZffkUgGyGTLPU0VW-nWld8z7P0H2Ru_lA2gyfCIuoaN7WmFU6IRQ9AVVBKNMpsRsxQkxp27qp4b1vr0Nu7xAxlXjinmqCYcWDyv6BlIGk1JID86YB5QMhEW98wyZ5sollRXTc">http://www.technology.ie</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Intl.
+353 (0) 59 9183072</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Direct
Dial: +353 (0)59 9183090</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Social:
<a moz-do-not-send="true"
href="https://protect-us.mimecast.com/r/c9ciyb99CMvSHLw2MJX2WYjWAGojFAv6abNbJNSbdh-ZFyKYiMOesCOSW0IbP_Hk74wcQMPR4LFdtPIo3qwpdVxkGjxnPEF73YlWOioKWfm0ASY6v7enF3zKmqddqH2G4dXIbPg_PVqGwzzZzhWQxKSK2MKPyc4QXazyYJjS7H_X2JdIq2B8eAZeCDmgPBWH09Ix-VujUi5pHJeE_GXWIlFrE4TTH0hP08WIPWYQvhY">http://mneylon.social</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">-------------------------------</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Blacknight
Internet Solutions Ltd, Unit
12A,Barrowside Business Park,Sleaty</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif"">Road,Graiguecullen,Carlow,Ireland
Company No.: 370845</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></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-family:"Calibri","sans-serif"">From:
</span> </b><span
style="font-family:"Calibri","sans-serif"">James
Gannon<br>
<b>Date: </b>Thursday 30 April 2015 07:45<br>
<b>To: </b>Graeme Bunton, "<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>Re: [Gnso-ppsai-pdp-wg] PPSAI
Comment Period and Section 1.3.3</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;line-height:150%;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">I
would personally like to see if there is
public traction for distinguishing between
sites directly processing financial
truncations and sites who use 3<sup>rd</sup>
parties for processing financial
transactions as this is a very important
distinction. A simple and I hope
non-controversial additional question to the
ones below:</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">If
so, should domains which use a third party
to process financial transactions (i.e
Paypal, Stripe), and thus do not directly
process financial information, be subject to
the same restrictions? </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">There
are strong existing distinctions both in
national laws and in regulations such as
PCI-DSS between these two forms.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif";color:#1F497D">-James
Gannon</span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid
#E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"
style="line-height:normal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext"><a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Graeme Bunton<br>
<b>Sent:</b> Tuesday, April 28, 2015
10:17 PM<br>
<b>To:</b> PPSAI<br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg]
PPSAI Comment Period and Section 1.3.3</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><span
lang="EN-GB">Thanks to all WG members for a
very productive call earlier today(and to
Steve for his chairing acumen). The
co-chairs and staff met this afternoon to
tie down two loose ends from the call.<br>
<br>
Regarding the deadline for public comments
on the Initial Report, we recognize there is
considerable support for extending the
public comment period to 60 days instead of
the standard 40 days on which we have all
been planning. We are prepared to agree to
this, but with the caveat that this will
have repercussions on the pace and intensity
of our work once public comments have been
received. Specifically, if the public
comment deadline is extended until July 3
(60 days after our publication date of May
4), we will need to plan on at least weekly
calls throughout July and August, some of
which may need to be more than an hour in
length, to review these comments and move
toward a Final Report. Otherwise, we
jeopardize the prospects for getting the
Final Report in front of the GNSO council no
later than the Dublin ICANN meeting. As was
noted on the call today, many additional
steps need to take place even after this WG
issues its Final Report before any new
accreditation system can be implemented, so
the time pressure imposed by the expiration
of the Interim Specification at the end of
next year is already real. <br>
<br>
Also, as previously announced over the past
few weeks, if any WG members (or group of
members) wish to submit a brief separate or
additional statement for inclusion in the
package posted for public comment next
Monday, such statements need to be received
by staff no later than Thursday, April 30. <br>
<br>
Lastly, the other loose end involves
proposed revisions to section 1.3.3 of the
Initial Report, which were presented on the
call earlier today but which we did not have
time to discuss fully. We agree that this
section could benefit from some revision,
but believe it should take the form of
greater concision, not additional
presentation of arguments for the divergent
positions. Thus we suggest that section
1.3.3 be revised to read as follows: <br>
<br>
---</span><o:p></o:p></p>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"
style="margin-bottom:12.0pt"><span
style="font-family:"Calibri","sans-serif""
lang="EN-GB">Although the WG agreed that
the mere fact that a domain name is
registered by a commercial entity or by
anyone conducting commercial activity
should not preclude the use of P/P
services , there was disagreement over
whether domain names that are actively
used for commercial transactions (e.g. the
sale or exchange of goods or services)
should be prohibited from using P/P
services. While most WG members did not
believe such a prohibition is necessary or
practical, some members believed that
registrants of such domain names should
not be able to use or continue using proxy
or privacy services.<br>
<br>
For those that argued that it is necessary
and practical to limit access to P/P
services to exclude commercial entities,
the following text was proposed to clarify
and define their position: “domains used
for online financial transactions for
commercial purpose should be ineligible
for privacy and proxy registrations.”<br>
<br>
Public comment is therefore specifically
invited on the following questions: </span>
<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
level1 lfo4"> <span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif""
lang="EN-GB">Should registrants of
domain names associated with commercial
activities and which are used for online
financial transactions be prohibited
from using, or continuing to use,
privacy and proxy services? </span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
level1 lfo4"> <span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif""
lang="EN-GB">If so, will it be useful to
adopt a definition of “commercial” or
“transactional” to define those domains
for which P/P service registrations
should be disallowed? And if so, what
should the definition(s) be?”</span><span
lang="EN-GB"> </span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2
level1 lfo4"> <span
style="font-size:11.0pt;line-height:150%;font-family:"Calibri","sans-serif""
lang="EN-GB">Will it be necessary to
make a distinction in the WHOIS data
fields to be displayed as a result?</span><o:p></o:p></li>
</ul>
</blockquote>
<p class="MsoNormal" style="line-height:normal"><span
style="font-family:"Times New Roman ,
serif","serif"">---<br>
Thanks,<br>
<br>
Graeme Bunton & Steve Metalitz<br>
<br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>_________________________<o:p></o:p></pre>
<pre>Graeme Bunton<o:p></o:p></pre>
<pre>Manager, Management Information Systems<o:p></o:p></pre>
<pre>Manager, Public Policy<o:p></o:p></pre>
<pre>Tucows Inc.<o:p></o:p></pre>
<pre>PH: 416 535 0123 ext 1634<o:p></o:p></pre>
</div>
</div>
<p class="MsoNormal" style="line-height:normal"><span
style="font-family:"Times New
Roman","serif";mso-fareast-language:EN-US"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre>
<pre><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="https://protect-us.mimecast.com/r/w4cOGJpN8aqiFBeZDDCfM61L9zSPPQ8yJTOsuokgr0uUoFWQcH4C1vKnhAJR8I5CDUGd3f75FQZ0RrGQoOiumi5fkuGEeAdPoDjA3DGFVt5fCde0OuGcKsc4syb-86Vd3ZsMEWNubiso-WCMGJKqofC67xfNJVO1oqFPAmL7abae98k88hH_BDY04YcHIhprEG-vGcToOzkceYzCw4sYw77Sj8DHh1iwNuJPKagRVm5XkaPrKRnvsIqURxFUU964UWsThNMfSE_TxYg9ZhC-Fg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal" style="line-height:normal"><span
style="font-family:"Times New
Roman","serif";mso-fareast-language:EN-US"><o:p> </o:p></span></p>
</div>
</div>
</blockquote>
<p class="MsoNormal" style="line-height:normal"><span
style="font-family:"Times New
Roman","serif";mso-fareast-language:EN-US"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://protect-us.mimecast.com/r/w4cOGJpN8aqiFBeZDDCfM61L9zSPPQ8yJTOsuokgr0uUoFWQcH4C1vKnhAJR8I5CDUGd3f75FQZ0RrGQoOiumi5fkuGEeAdPoDjA3DGFVt5fCde0OuGcKsc4syb-86Vd3ZsMEWNubiso-WCMGJKqofC67xfNJVO1oqFPAmL7abae98k88hH_BDY04YcHIhprEG-vGcToOzkceYzCw4sYw77Sj8DHh1iwNuJPKagRVm5XkaPrKRnvsIqURxFUU964UWsThNMfSE_TxYg9ZhC-Fg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal" style="line-height:normal"><span
style="font-family:"Times New
Roman","serif";mso-fareast-language:EN-US"><o:p> </o:p></span></p>
</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>
<pre class="moz-signature" cols="72">--
_________________________
Graeme Bunton
Manager, Management Information Systems
Manager, Public Policy
Tucows Inc.
PH: 416 535 0123 ext 1634</pre>
<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>
</body>
</html>