[gnso-rap-dt] Meta-Issue -- Best Practices Collection and Dissemination
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hello everyone!</div><div><br></div><div>I'm going to take advantage of Mikey getting his homework assignment out earlier to completely plagiarize his rather nice format and concept framing to cover the "best practices" meta-issue we discussed on last week's call. Thanks Mikey! This is a start, and I've left some room for more analysis, but I think I captured what we discussed, and what I've been thinking the ICANN "world" has needed for quite a while now. Anyway, more food for thought/content to criticize/ideas to explore.</div><div><br></div><div>Best,</div><div><br></div><div>Rod</div><div><br></div><div><span class="Apple-style-span" style="font-size: 12px; "><div>Rod Rasmussen</div><div>President and CTO</div><div>Internet Identity</div></span></div><div>- - - - - - - - -</div><div><br></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<o:p></o:p></span></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">This working group has begun identifying “meta-issues” which are turning up in a 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"> </span>These meta-issues have a number of attributes in common:</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto; text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </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:l2 level1 lfo2"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>They are being discussed in several working and advisory groups simultaneously</p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space: auto;text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Previous working and advisory groups have discussed these issues without full resolution</p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto; text-indent:-.25in;mso-list:l2 level1 lfo2"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </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"><b style="mso-bidi-font-weight:normal"><o:p> </o:p></b></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"><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"><b style="mso-bidi-font-weight:normal"><span style="font-size:14.0pt;mso-bidi-font-size:12.0pt">Meta-issue – Collection and Dissemination of “Best Practices”<o:p></o:p></span></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">The working group has identified the need for the domain registration community to collect “best practices” in many aspects of domain name registration and management for various participants in the field into some sort of knowledge base.<span style="mso-spacerun: yes"> </span>Further, an efficient means to disseminate these practices to all the appropriate members of the ICANN community is desired.<span style="mso-spacerun: yes"> </span>Best practices should also be kept current and relevant.<span style="mso-spacerun: yes"> </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 has potential impact for almost any current and future working or advisory group.</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Definition of “Best Practices”<o:p></o:p></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">From Wikipedia (<a href="http://en.wikipedia.org/wiki/Best_practices";>http://en.wikipedia.org/wiki/Best_practices</a>): </p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal" style="margin-left:.5in"><i style="mso-bidi-font-style:normal"><span style="font-size:11.0pt;mso-bidi-font-size:12.0pt">A best practice is a technique, method, process, activity, incentive, or reward that is believed to be more effective at delivering a particular outcome than any other technique, method, process, etc. when applied to a particular condition or circumstance. The idea is that with proper processes, checks, and testing, a desired outcome can be delivered with fewer problems and unforeseen complications. Best practices can also be defined as the most efficient (least amount of effort) and effective (best results) way of accomplishing a task, based on repeatable procedures that have proven themselves over time for large numbers of people.<o:p></o:p></span></i></p><p class="MsoNormal" style="margin-left:.5in"><i style="mso-bidi-font-style:normal"><span style="font-size:11.0pt;mso-bidi-font-size:12.0pt"><o:p> </o:p></span></i></p><p class="MsoNormal" style="margin-left:.5in"><i style="mso-bidi-font-style:normal"><span style="font-size:11.0pt;mso-bidi-font-size:12.0pt">A given best practice is only applicable to particular condition or circumstance and may have to be modified or adapted for similar circumstances. In addition, a "best" practice can evolve to become better as improvements are discovered.<o:p></o:p></span></i></p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal"><o:p> </o:p></b></p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal">The Problem<o:p></o:p></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">A number of working and advisory groups are coming up with many good ideas for tackling a wide variety of problems in the industry.<span style="mso-spacerun: yes"> </span>The group’s participants often label these ideas as “best practices”.<span style="mso-spacerun: yes"> </span>However, many of these ideas do not lend themselves well to crafting as policy, for they are often narrow in scope, limited in the time they could be effective, or difficult to capture as policy concepts or contract terms.<span style="mso-spacerun: yes"> </span>This is particularly true in the areas surrounding abuse and malicious use.<span style="mso-spacerun: yes"> </span>Yet all industry participants could benefit greatly by adopting many of these best practices.<span style="mso-spacerun: yes"> </span>Unfortunately, no formal mechanisms for collecting such practices, keeping them updated, or disseminating them to all relevant industry participants exists today within the ICANN community.<span style="mso-spacerun: yes"> </span>Thus, much of the good work done in these groups is not captured effectively if it is not included in their policy-making outcomes.</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Analysis<o:p></o:p></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Some more details, examples, and possible models.</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Who is in the best position to collect/store/update/disseminate?<span style="mso-spacerun: yes"> </span>ICANN staff, Constituencies, specialized committee, 3<sup>rd</sup> parties?</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Some examples – SSAC documents, IETF, APWG BP for registrars.</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">How do people do this today in a formalized fashion?<span style="mso-spacerun: yes"> </span>What are the “best practices” for handling best practices across industries?</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">How “binding” should best practices be?<span style="mso-spacerun: yes"> </span>Audit/report on adoption?<span style="mso-spacerun: yes"> </span>Ways to recognize industry leaders?</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Best practices in the field of anti-abuse or security are necessary but often lose their effectiveness in relatively short amount of time.<span style="mso-spacerun: yes"> </span>This does not lend well to formal policy, but augers for the collection of effective techniques and sharing of that information with peers in the field.</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">Best practices in the field of anti-abuse or security are often very sensitive, and industry participants would not like many of them made public so that bad actors could learn from them and adapt new tactics.<span style="mso-spacerun: yes"> </span>How can sensitive best practices be safely disseminated to industry participants?<span style="mso-spacerun: yes"> </span>How can the veracity of all industry participants be assured as well?</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Recommendation<o:p></o:p></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">The working group suggests that this “meta-issue” be addressed either by a PDP working group or an ICANN advisory group, with the goals of:</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto; text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Creating mechanisms within the ICANN community for formal collection of best practices in key disciplines.</p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space: auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Establishing processes for updating best practices over time.</p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space: auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Creating multiple channels (some private/secure) for dissemination of best practices to all relevant community members.</p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space: auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Incorporating the gathering and recommendation of best practices into the processes used by various policy and advisory working groups.</p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space: auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Instituting practices to measure and incentivize adoption of best practices across the industry.</p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto; text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Launching regular review processes where universal best practices may be incorporated into more formal policies.</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><b style="mso-bidi-font-weight:normal">Scope of discussion<o:p></o:p></b></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">A number of prior, and currently running policy groups are discussing this issue in one form or another.<span style="mso-spacerun: yes"> </span>Subsequent discussions should, at a minimum, include interested stakeholders from:</p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto; text-indent:-.25in;mso-list:l1 level1 lfo3"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>Fast Flux working group</p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space: auto;text-indent:-.25in;mso-list:l1 level1 lfo3"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </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 lfo3"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </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 lfo3"><span style="mso-bidi-font-family:Cambria"><span style="mso-list:Ignore">-<span style="font:7.0pt "Times New Roman""> </span></span></span>The relevant GNSO process-reform working groups</p> <!--EndFragment--> </div><div><br> </div> </body></html> Attachment:
RAP - Meta-Issue - Best Practices.doc <html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "></body></html>
|