ICANN ICANN Email List Archives

[gnso-rap-dt]


<<< Chronological Index >>>    <<< Thread Index >>>

[gnso-rap-dt] Meta-Issue -- Policy-Violation Reporting

  • To: Registration abuse list ICANN <gnso-rap-dt@xxxxxxxxx>
  • Subject: [gnso-rap-dt] Meta-Issue -- Policy-Violation Reporting
  • From: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Date: Sun, 10 Jan 2010 10:00:22 -0600

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: 
space; -webkit-line-break: after-white-space; "><div>hi 
gang,</div><div><br></div><div>here's a draft for you to review -- this one 
replaces Recommendation-3 of the UofC draft with a description of a 
"meta-issue" around policy-violation reporting, tracking, compliance. &nbsp;i 
also to a stab at a paragraph to introduce the "meta issue" 
concept.</div><div><br></div><div>tip of the hat to Berry for editorial 
review.</div><div><br></div><div>mikey</div><div><br></div><div>- - - - - - - - 
-</div><div><!--StartFragment--><p class="MsoNormal"><b 
style="mso-bidi-font-weight:normal"><span 
style="font-size:16.0pt;mso-bidi-font-size:12.0pt">Meta Issues</span></b></p><p 
class="MsoNormal">This working group has begun identifying “meta-issues” which
are turning up in number of GNSO working-groups (RAP, IRTP-B and PEDNR) and
ICANN advisory-groups (High Security TLD and Zone File Access) at the same
time.<span style="mso-spacerun: yes">&nbsp;&nbsp; </span>These meta-issues have
a number of attributes in common:</p><p class="MsoListParagraphCxSpFirst" 
style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l3 level1 lfo3"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Their
scope spans a number of ICANN policies</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l3 level1 lfo3"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>They
are being discussed in several working and advisory groups simultaneously</p><p 
class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l3 level1 lfo3"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>They
are worthy of substantive discussion and action, but may not lend themselves to
resolution through current policy processes</p><p class="MsoNormal" 
align="center" style="text-align:center"><b style="mso-bidi-font-weight:
normal"><span 
style="font-size:14.0pt;mso-bidi-font-size:12.0pt">______________<o:p></o:p></span></b></p><p
 class="MsoNormal" align="center" style="text-align:center"><font 
class="Apple-style-span" size="6"><span class="Apple-style-span" 
style="font-size: 19px;"><b><br></b></span></font></p><p class="MsoNormal"><b 
style="mso-bidi-font-weight:normal"><span 
style="font-size:14.0pt;mso-bidi-font-size:12.0pt">Meta-issue – Uniformity of
reporting</span></b></p><p class="MsoNormal">The working group has identified 
the need for more
uniformity in the mechanisms to initiate, track and analyze policy-violation
reports.<span style="mso-spacerun: yes">&nbsp; </span>This recommendation is a
“meta-issue” because it is much broader than registration abuse, is being
discussed by a number of working and advisory groups simultaneously and will
require more than simple uniformity of contracts to address.</p><p 
class="MsoNormal"><b style="mso-bidi-font-weight:normal">The Problem</b></p><p 
class="MsoNormal">A number of working and advisory groups are finding their
work hampered by the lack of reliable (rather than anecdotal) data upon which
to base policy decisions.<span style="mso-spacerun: yes">&nbsp;
</span>End-users and registrants find it confusing and difficult to identify
the most appropriate reporting venue or action when they experience
problems.<span style="mso-spacerun: yes">&nbsp; </span>Registrars and
registries are frustrated when their customers file complaints in error, in the
wrong place or without first seeking help from the provider.<span 
style="mso-spacerun: yes">&nbsp;</span></p><p class="MsoNormal"><b 
style="mso-bidi-font-weight:normal">Recommendation</b></p><p 
class="MsoNormal">The working group suggests that this “meta-issue” be
addressed either by a PDP working group, a best-practices working group or an
ICANN advisory group, with the goals of:</p><p 
class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo2"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Providing
“just in time” education and knowledge to people wanting to report 
problems</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo2"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Making
it easier to submit a valid complaint and reducing the number of erroneous 
ones</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo2"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Improving
the effectiveness of policy-compliance activities</p><p 
class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo2"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Improving
the data available for GNSO (working-group) and ICANN (advisory-group)
policy-making </p><p class="MsoListParagraphCxSpLast" 
style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo2"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Answering
the question “which comes first, policy-process or definitive data describing
the problem?” along with suggestions as to how data can be gathered when it
hasn’t yet been included in the reporting process.</p><p class="MsoNormal">The 
working group suggests, as a starting point for
discussion, that <u>every</u> policy should have:</p><p 
class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l2 level1 lfo1"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><b 
style="mso-bidi-font-weight:normal">Reporting</b> – a mechanism whereby
violations of the policy can be reported by those who are impacted </p><p 
class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l2 level1 lfo1"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><b 
style="mso-bidi-font-weight:normal">Notification </b>– standards as to how
contracted parties make visible;</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:1.0in;mso-add-space:
auto;text-indent:-.25in;mso-list:l2 level2 lfo1"><span 
style="font-family:&quot;Courier 
New&quot;;mso-fareast-font-family:&quot;Courier New&quot;;
mso-bidi-font-family:&quot;Courier New&quot;"><span 
style="mso-list:Ignore">o<span style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp; </span></span></span>where
to report policy violations </p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:1.0in;mso-add-space:
auto;text-indent:-.25in;mso-list:l2 level2 lfo1"><span 
style="font-family:&quot;Courier 
New&quot;;mso-fareast-font-family:&quot;Courier New&quot;;
mso-bidi-font-family:&quot;Courier New&quot;"><span 
style="mso-list:Ignore">o<span style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp; </span></span></span>definitions
of what constitutes a “reportable” problem</p><p 
class="MsoListParagraphCxSpMiddle" style="margin-left:1.0in;mso-add-space:
auto;text-indent:-.25in;mso-list:l2 level2 lfo1"><span 
style="font-family:&quot;Courier 
New&quot;;mso-fareast-font-family:&quot;Courier New&quot;;
mso-bidi-font-family:&quot;Courier New&quot;"><span 
style="mso-list:Ignore">o<span style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp; </span></span></span>reporting
or action options that are available when the person’s problem falls outside
ICANN policy </p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l2 level1 lfo1"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><b 
style="mso-bidi-font-weight:normal">Tracking </b>– transparent processes to
collect, analyze and publish summaries of valid policy-violation reports</p><p 
class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l2 level1 lfo1"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><b 
style="mso-bidi-font-weight:normal">Compliance </b>– processes to provide
due-process, and sanctions that will be applied, in the case of 
policy-violations</p><p class="MsoNormal"><b 
style="mso-bidi-font-weight:normal">Scope of discussion</b></p><p 
class="MsoNormal">A number of currently running policy groups are discussing
this issue in one form or another.<span style="mso-spacerun: yes">&nbsp;
</span>Subsequent discussions should, at a minimum, include interested
stakeholders from:</p><p class="MsoListParagraphCxSpFirst" 
style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l1 level1 lfo4"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>RAP
working group</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l1 level1 lfo4"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>PEDNR
working group</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l1 level1 lfo4"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>IRTP-B
working group</p><p class="MsoListParagraphCxSpMiddle" 
style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l1 level1 lfo4"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>High
Security TLD advisory group</p><p class="MsoListParagraphCxSpLast" 
style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l1 level1 lfo4"><span 
style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span 
style="font:7.0pt &quot;Times New 
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>The
relevant GNSO process-reform working groups</p></div><div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; 
-webkit-line-break: after-white-space; "><span class="Apple-style-span" 
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; 
font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; 
letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; 
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; 
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; 
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; 
-webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; 
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span 
class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); 
font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: 
normal; font-weight: normal; letter-spacing: normal; line-height: normal; 
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; 
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; 
-webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; 
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div 
style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: 
after-white-space; "><span class="Apple-style-span" style="border-collapse: 
separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; 
font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: 
normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: 
none; white-space: normal; widows: 2; word-spacing: 0px; 
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; 
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; 
-webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; 
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>- - - - 
- - - - -</div><div>phone<span class="Apple-converted-space">&nbsp;</span><span 
class="Apple-tab-span" style="white-space: pre; ">     </span>651-647-6109 
&nbsp;</div><div>fax &nbsp;<span class="Apple-tab-span" style="white-space: 
pre; ">         </span>866-280-2356 &nbsp;</div><div>web<span 
class="Apple-converted-space">&nbsp;</span><span class="Apple-tab-span" 
style="white-space: pre; ">       </span><a 
href="http://www.haven2.com";>www.haven2.com</a></div><div>handle<span 
class="Apple-tab-span" style="white-space: pre; ">      </span>OConnorStP (ID 
for public places like Twitter, Facebook, Google, 
etc.)</div></div></span></div></span></div></span></div>
</div><div><br class="webkit-block-placeholder"></div><div><br></div>
</body></html>

Attachment: RAP - Meta-Issue - Reporting v2.doc
Description: MS-Word document

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: 
space; -webkit-line-break: after-white-space; "></body></html>


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy