<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="Tiki CMS/Groupware via FeedCreator 1.7.2.1" -->
<?xml-stylesheet href="http://wiki.chapters.isoc.org/lib/rss/rss-style.css" type="text/css"?>
<?xml-stylesheet href="http://wiki.chapters.isoc.org/lib/rss/rss20.xsl" type="text/xsl"?>
<rss version="2.0">
    <channel>
        <title>Tiki RSS feed for weblogs</title>
        <description></description>
        <link>http://wiki.chapters.isoc.org/tiki-blogs_rss.php?ver=2</link>
        <lastBuildDate>Sun, 22 Nov 2009 17:33:55 +0100</lastBuildDate>
        <generator>Tiki CMS/Groupware via FeedCreator 1.7.2.1</generator>
        <image>
            <url>http://wiki.chapters.isoc.org/styles/isoc/ilogo.gif</url>
            <title>Internet Society (ISOC)</title>
            <link>http://wiki.chapters.isoc.org/tiki-index.php</link>
            <description><![CDATA[Feed provided by Internet Society (ISOC). Click to visit.]]></description>
        </image>
        <language>en</language>
        <managingEditor>ISOC</managingEditor>
        <webMaster>webmaster@isoc.org</webMaster>
        <item>
            <title></title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=2&amp;postId=5077</link>
            <description><![CDATA[This blog is now CLOSED.<br />
]]></description>
            <author>lord</author>
            <pubDate>Tue, 08 Sep 2009 05:33:12 +0100</pubDate>
        </item>
        <item>
            <title></title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=4&amp;postId=5076</link>
            <description><![CDATA[This blog is now CLOSED.<br />
]]></description>
            <author>lord</author>
            <pubDate>Tue, 08 Sep 2009 05:30:18 +0100</pubDate>
        </item>
        <item>
            <title>Feedback on &quot;Best Practice Guidelines&quot; document and Version 1.1 of Consultation Draft</title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=2&amp;postId=4207</link>
            <description><![CDATA[Dear Colleagues,<br />
<br />
The Sphere consult group opened this blog on January 29th 2009 to collect comments on a draft process prepared by the group for Consultation between ISOC Global and ISOC Chapters. Since that time, comments have been collected on the blog, discussion has taken place in the Sphere Consult group, the process has been used by Bill Graham (ISOC staff) and more recently Christine Runnegar (ISOC staff) and a revised draft (version 1.1) incorporating comments has been produced and is posted to the blog below.<br />
<br />
The group has also produced a "Best Practice template" aimed at helping and guiding anyone wishing to initiate a consultation.<br />
<br />
Feedback is now sought on both documents and the blog will remain open for one month until 5th August. The final documents will be sent to the Sphere SIT team for review and handing to the ISOC Executive Team.<br />
<br />
On behalf of the Sphere Consult group, further comments are invited on two documents:<br />
<br />
1. Version 1.1 of the 'Consultation draft'<br />
2. “Best Practice” summary guidelines for conducting a Consultation in ISOC<br />
<br />
The final documents will be available in Spanish and French as well as English.  Thank you to everyone who has provided valuable feedback. Thanks also to the Sphere Consult team.<br />
]]></description>
            <author>lord</author>
            <pubDate>Wed, 08 Jul 2009 05:22:05 +0100</pubDate>
        </item>
        <item>
            <title>“Best Practice” summary guidelines for conducting a Consultation in ISOC</title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=2&amp;postId=4178</link>
            <description><![CDATA[“Best Practice” summary guidelines for conducting a Consultation in ISOC<br />
<br />
Drafted by the Sphere-Consult team<br />
<br />
Version 1.0<br />
<br />
This template is offered to anyone wishing to initiate a consultation within ISOC. It is suggested as a “best practice” template.<br />
<br />
1.  Statement<br />
Title:<br />
Purpose:<br />
Consulting who: seeking high level or skilled group, which stakeholder groups?<br />
Initiated by:<br />
Triggered by:<br />
<br />
2. Process details<br />
Tools used: (blog, mailing list, survey – send URL )<br />
Stage of consultation:<br />
<br />
<br />
3. Description<br />
Short summary of issue(s) to be addressed:<br />
Summary in French (if applicable):<br />
Summary in Spanish (if applicable):<br />
Full details: (if applicable)<br />
<br />
<br />
4. Timelines<br />
Deadline for feedback:<br />
Timelines:<br />
Privacy needed:<br />
<br />
5. Additional information<br />
References:<br />
Other relevant information:<br />
<br />
]]></description>
            <author>lord</author>
            <pubDate>Wed, 08 Jul 2009 04:30:34 +0100</pubDate>
        </item>
        <item>
            <title></title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=2&amp;postId=4174</link>
            <description><![CDATA[Consultation<br />
<br />
A Proposal from the Sphere-Consult Group<br />
<br />
Version 1.1 (incorporating feedback)<br />
<br />
1. Introduction<br />
This is version 1.1 of this document. Please see appendix 2 for details of the feedback received and how it was incorporated into this document.<br />
<br />
1.1 Our Goal – Development and Implementation of Policy Consultation Protocol<br />
<br />
The Internet Society needs protocols and/or procedures in place for how to conduct a consultation with and among its various constituencies – chapters, organizational members, and individual members - on policy issues. There is no clear protocol for how a chapter may consult with ISOC Global and/or the other chapters about an impending event or development in its local region. Our charge was to devise a draft set of protocols for the conduct of policy consultations between and among ISOC Global and its constituencies.<br />
<br />
In addition to considering the above relationships, the group did some broader thinking about other consultations – exploring ISOC's various constituencies and the need to collect opinions that would be desirable within the ISOC context. These include interactions between and among the following groups: the ISOC Board, staff, advisory council, regional offices, associate organizations like ISOC-ECC, and chapters.<br />
<br />
2. Proposed Consultation Process<br />
<br />
2.1 Who is consulting<br />
<br />
For the purposes of this document, we initially limited the consultation process discussion to ISOC Global and ISOC Chapters. However, we do feel that this consultation process could easily engage multiple stakeholder groups simultaneously as discussed in the previous paragraph. Hence, this document addresses consultation throughout ISOC.<br />
<br />
2.2 Business Process Requirements for Consultations<br />
<br />
2.2.1	Trigger for a consultation<br />
<br />
Different triggers for a consultation can be classified as:<br />
<br />
a)	issues arise locally only<br />
b)	issues arise locally but have more interest broadly<br />
c)	international issues<br />
<br />
Within these categories, triggers can be external (from an inquiry, discussion paper etc) arising from issues by Government or other organisations.<br />
<br />
Triggers can be rated by their importance to the organisation. Is it critical? Is it important that certain stakeholder groups respond? Are there external timelines imposed?<br />
<br />
2.2.2 Planning and Timing of consultations is critical.<br />
<br />
Because of global nature of ISOC, planning and timing of consultations needs to be carefully considered. Policy issues have different regional importance at different times. During a consultation, the participants need to engage at a speed which fits with their local needs or the global needs of ISOC Global.<br />
<br />
We recommend:<br />
• A standard consultation be communicated with appropriate parties at least one month before a final decision is needed.<br />
<br />
2.2.3 Engagement expectations need to be set as part of a consultation.<br />
<br />
In any engagement, the body initiating a consultation must inform its target audience very specifically about their expectations during the consultation. This includes but is not limited to the following expectations:<br />
<br />
• Timing/due dates<br />
• Who is being consulted as part of the process<br />
• What is the purpose of the consultation – who is the ultimate audience<br />
• How a final decision will be made<br />
• What the consultees are expected to provide: advice, ideas, etc.<br />
• The stage of the consultation: dialogue, discussion, decision (see Section 2.3)<br />
<br />
2.2.4 Appropriate tools must be used to archive consultations for future use.<br />
<br />
Consultations, and the discourse and discussion that surround them, have a tremendous value to ISOC. As such, ISOC must support a discussion forum structure that allows for archival features, participation by and identification of participants, and multiple access methods (online, email, web-based, universal-design-qualified, etc.)<br />
<br />
2.2.5 Consultation with other participants must be identified and shared with all participants.<br />
<br />
ISOC Global and its various constituencies understand that multiple sets of stakeholders may be interested in being included in key policy consultations. The organizational entity asking for the consultation needs to identify these other participants and share this information with all participants. Our group recognized that consultations would likely involve interactions between and among the many groups: the ISOC Board, staff, advisory council, regional offices, associate organizations like ISOC-ECC, chapters, the ISOC Advisory Counsel, and ISOC’s organizational members.<br />
<br />
2.3 Consultation process<br />
<br />
Through this process, participants will be able to map out the likely consequences of decisions, work out the importance of individual factors, and choose the best course of action to take. We are proposing a three level consultative model based on dialogue and discussion and resulting in a valued, shared decision.<br />
<br />
2.3.1 Step One: Dialogue &mdash; understanding the different perspectives<br />
<br />
The physicist David Bohm, who devoted his last years to the investigation of dialogue, described it this way. Dialogue is "not an exchange and it’s not a discussion. Discussion means batting it back and forth like a ping pong game. That has some value, but in dialogue we try to go deeper…to create a situation where we suspend our opinions and judgements in order to be able to listen to each other."<br />
<br />
During the dialogue phase of a consultation, the participants need to engage with each other in an open way and learn how an issue is perceived from a variety of difference perspectives. The dialogue phase of a consultation is possibly the most important phase since it allows one to view many different sides of the same issue. This phase should be done in an open, encouraging and respectful manner to ensure that as many perspectives as possible are considered in later phases.<br />
<br />
2.3.2 Step Two: Discussion &mdash; examining the competing values from the perspectives<br />
<br />
During the discussion phase of the consultation, participants need to weigh the competing perspectives collected during the dialogue phase against the consultation goals and the ISOC Principles. It might be that this part of the consultation could be done with a smaller group to hasten progress. But, the value of the process itself and the discussion is important for archival purposes and for future references. As such, we encourage an open and respectful forum for this phase.2.3.3<br />
<br />
Step 3: Decision - choices made in the best interest of the ISOC principles<br />
<br />
Once a final decision is made, it should be documented in a formal document that is archived along with the dialogue and discussion that lead to the decision. The final document should outline how the decision supports the ISOC principles and its importance to the future of the Internet.<br />
<br />
2.3.4 Structure of the Consultation Process<br />
<br />
We recommend that consultations be conducted by forming ad-hoc and short-lived purpose-built groups of interested stakeholders that are aware of the Consultation Fundamentals outlined in Appendix A. It is envisioned that a standard consultation will involve proactive consideration of issues with adequate time for stakeholder engagement following the three steps outlined below. A reactive consultation process should only be in response to an immediate crisis and should still encompass many of the attributes discussed herein. Reactive processes may have shorter timeframes and a more targeted stakeholder group focus in order to meet tight deadlines.<br />
<br />
2.3.5 Consultation Milestones and Activities<br />
<br />
The consultation should be framed so that the participating community understands the nature of the consultation.<br />
<br />
• For Information: The statement is to inform the participant of something and expects no response. <a class="wiki"  href="rarely used in a consultation process?PHPSESSID=6dd571959ec6e97e127ba9fbd2d09961" rel="">rarely used in a consultation process</a><br />
• For Dialogue: The statement requests dialogue from the addressee, usually within a stated time frame.<br />
• For Discussion: The statement requests discussion from the addressee, usually within a stated timeframe.<br />
• For Decision: The statement includes a decision and expects no further response.<br />
<br />
A reasonable consultation process will consist of the following activities.<br />
<br />
1.	Create a statement of what is being asked<br />
2.	Create a statement of the proposed position (if appropriate)<br />
3.	Assure that the statement is consistent with ISOC's core principles and the current ISOC Global Strategic Operating Plan.<br />
4.	Identify the participants needed for a robust consultation process.<br />
5.	Set a timeline for a discussion process and review.<br />
6.	Publicize the consultation by including the following information in an appropriate forum:<br />
<tt>       • who is asking</tt><br />
<tt>       • the intended recipient of the final policy</tt><br />
<tt>       • the point of contact for questions and responses</tt><br />
<tt>       • what is expected of the participants</tt><br />
<tt>       -	is this strictly informative?</tt><br />
<tt>       -	is this for comment?</tt><br />
<tt>       -	is a specific action required?</tt><br />
<tt>       -	Acknowledgment/interest in participation</tt><br />
<tt>       -	what constitutes a useful reply</tt><br />
<tt>       • Important deadlines for dialogue, discussion, final policy formation and documentation</tt><br />
<br />
7.	Is any part of the consultation private? If so, please indicate this.<br />
<br />
If participants find the proposed deadline unreasonable, they should reply immediately with a date that they think they can achieve, and then act accordingly barring further communication from the requester.<br />
<br />
2.4 Electronic Support for a Robust Consultation Process<br />
<br />
Because of ISOC’s global nature and the widespread worldwide distribution of chapters, the need for translation support and the various levels of engagement of chapters, it is necessary to have a robust online toolset that will make consultation easy for all members of ISOC. Basically, a discussion forum needs to be created that:<br />
<br />
•	Makes it easy to ask for input,<br />
•	Makes it easy to track the input even if you weren't watching realtime, and<br />
•	Makes it easy to archive the results for future reference.<br />
<br />
<br />
Appendix A: Consultation Fundamentals<br />
1. The ISOC Principles are shared core values utilized in policy formation but could use a revamp.<br />
The group agreed that all chapters, ISOC global and other members of ISOC should agree to and use the ISOC principles as the common ideas and shared values that we all respect and utilize as the underpinnings of all policies.<br />
ISOC's activities are founded upon, and driven by, the following principles:<br />
<br />
•	Open, unencumbered, beneficial use of the Internet.<br />
•	Self-regulated content providers; no prior censorship of on-line communications.<br />
•	On-line free expression is not restricted by other indirect means such as excessively restrictive governmental or private controls over computer hardware or software, telecommunications infrastructure, or other essential components of the Internet.<br />
•	Open forum for the development of standards and Internet technology.<br />
•	No discrimination in use of the Internet on the basis of race, color, gender, disability, language, religion, political or other opinion, national or social origin, property, birth, or other status.<br />
•	Personal information generated on the Internet is neither misused nor used by another without informed consent of the principal.<br />
•	Internet users may encrypt their communication and information without restriction.<br />
•	Encouragement of cooperation between networks: connectivity is its own reward; therefore network providers are rewarded by cooperating with each other.<br />
<br />
However, the group also thought that these principles needed to be revisited as they are seen as North American-centric. The principles could be made a stronger, foundational set of values if they were amended to reflect a more global perspective.<br />
<br />
2.  Policy decisions, even when considered relatively minor, should be shared amongst the parties.<br />
One of the interesting ideas that emerged during our dialogue was that policy decisions should be allotted adequate time for discussion, dialogue and/or distribution. Parties need to be given adequate time to digest information and determine the need to share amongst their colleagues.<br />
<br />
3.  Mutual respect for roles and responsibilities are fundamental to a positive collaboration process.<br />
The group discussed a number of instances in the past where there was a conflict in policy between ISOC Global and the chapters. In the course of our dialogue, it became clear that a fundamental recognition of roles and responsibilities needed to be understood and respected both from the ISOC Global side and from the chapter side.<br />
In order for consultations to take place that allow for the best exchange of ideas, a genuine trust relationship needs to be in place among the parties that are participating in the consultation. This “fabric of relationships” is fundamental to success. The participants in a consultation need to understand and respect the values, the passions and the time available for each individual.<br />
<br />
The chapter representatives are usually volunteers with “day-jobs.” At the same time, many have very strong local and/or regional liaison relationships and may need to have a reasonable amount of time allotted to ensure that new policies are framed and understood in a local context.<br />
<br />
The ISOC Global staff is under enormous pressure to deliver policy statements that support the ongoing education of policymakers worldwide to ensure that the Internet can support the next billion users. Its policy recommendations are based on the principles. Occasionally, these recommendations may have to be developed with swiftness to ensure that an immediate need for education and advice is met. Swift policy development should be the exception not the rule. Most policies can be developed in a thoughtful, well-timed, collaborative process based on mutual respect &mdash; where each participant is willing to look at things from another perspective and understands our shared common ideas and values that underlie the consultation.<br />
<br />
4.  Language is a major issue.<br />
Many of the chapter participants are not native English speakers. As such, when an important policy consultation is needed, it is imperative that the time and translation requirements be understood and respected on both sides of the consultation. In an important consultation, where there may be significant local issues or socialization of ideas needed, the chapters must be given either translated materials or adequate time to translate the ideas into locally understood concepts.<br />
<br />
5. The concept of subsidiarity should be employed by ISOC participants for consultations.<br />
<br />
The subsidiarity principle is based upon the autonomy and dignity of the human individual, and holds that all other forms of society, from the family to the state and the international order, should be in the service of the human person. Within ISOC, subsidiarity assumes that Internet users are the focus of our work, and emphasizes the importance of chapters and organizational members acting as regional or vertical market mediating structures which empower individual action and link the individual to society as a whole. "Positive subsidiarity” is the ethical imperative for ISOC HQ to advise globally on methods to create the policy and technical conditions necessary in the Internet for the benefit of the Internet user, based on ISOC’s principles.<br />
<br />
Appendix B: Summary comments from Blog &amp; responses:<br />
<br />
a) kshatriy says the document has "intricate language and academic thought" and should be "simple guidelines, simple language"<br />
<br />
Response: Ask Communications team to edit the final documents to provide simple guidelines and simple language<br />
<br />
b) In an actual consultation, in mexico people felt the need to summarise the issue at hand in a consultation, in one short paragraph in different languages - to help understanding of issues for non native english speakers<br />
<br />
Response: Included in revised draft and summary document<br />
<br />
c) There were 2 calls for timeframes to be clearer<br />
<br />
Response: Suggested standard timeline of one month was highlighted.<br />
<br />
d) Triggers for a consultation - Louis had some comments about that in his posting and using a question to help decide ie. whether it was critical or not to ISOC.<br />
<br />
Response: incorporated the comments based on suggestions.<br />
<br />
e) A couple of people mentioned the need for distinctions between private consultations which are sometimes part of the process - this could be referenced in a companion draft.<br />
<br />
Response: This is included in the guidelines document and in the Proposal<br />
<br />
f) Other than that there were suggestions for edits.<br />
<br />
Response: incorporated where possible.<br />
<br />
g) Rules of engagement for policy development process as raised by Ian Peter.<br />
<br />
Response: out of scope of this document as it is not about policy development. Fred felt that the board should be made aware that there is a call for this and this will be included in the covering email to the Executive Team.<br />
<br />
h) Suggestion by Holly Raiche to split elements of point 1 of 2.3.5 ‘Consultation milestones and activities “I’d split these elements.  The first item should be the statement of what is being asked – what is the issue.  The proposed position is quite different.”<br />
<br />
Response: The text was amended to read:<br />
1. Create a statement of what is being asked<br />
2. Create a statement of the proposed position (if appropriate).<br />
<br />
i) Triggers for a consultation – section 2.2.1<br />
Holly Raiche suggested to add text to clarify the source of a trigger.<br />
<br />
Response: The following text was added:  “Within these categories, triggers can be external (from an inquiry, discussion paper etc) arising from issues by Government or other organisations.”<br />
<br />
<br />
]]></description>
            <author>lord</author>
            <pubDate>Wed, 08 Jul 2009 04:25:05 +0100</pubDate>
        </item>
        <item>
            <title></title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=3&amp;postId=252</link>
            <description><![CDATA[Veni wrote:<br />
<br />
9. All parties adhere to ISOC’s Code of Individual Member Conduct <a class="wiki"  href="http://www.isoc.org/members/codeconduct.shtml">http://www.isoc.org/members/codeconduct.shtml</a><br />
<div class="simplebox">Question by Veni: <i>WHO are these "all parties"? Isn't this supposed to be ISOC Global and its Chapters? Or it includes the members? In the case they sign up to become ISOC Global members, they agreee to the Individual Member Conduct, right? </i></div><br />
<br />
Good catch Veni. It should just say "ISOC's individual members agree to the "Individual member code of conduct" -Anne<br />
]]></description>
            <author>lord</author>
            <pubDate>Thu, 11 Jun 2009 05:18:12 +0100</pubDate>
        </item>
        <item>
            <title>Post, Monolog or Dialog</title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=2&amp;postId=251</link>
            <description><![CDATA[Having been on originating end of creating online communities (anyone remember the IBM SIG on Compuserve?) and encouraging multiple person participation in the identification and resolution of many technical and social things, one of the items I would like to see added to this blog feature is a way to have associated / threaded dialog for the major items posted to the various blogs.<br />
<br />
Without a serious intention of getting involved and expressing one's perspectives, recommendations and suggestions, it is not as obvious to a new user just what to do to get involved with one or more of the very important items posted to the blogs.<br />
<br />
For instance, this is obviously a post to the "Consultation about a Consultations Process" Blog but no other context, perspective or views can be related to this post.  Going back to the Blog itself, since Anne and Frank are the only one's who have posted so far, this must somehow be related to one of these but what does that mean?<br />
<br />
What I would really like to see is a way for everyone to get involved, be heard, and easily identify any context associated with the particular "post" what ever that term means in this particular context...<br />
<br />
Mike Todd<br />
]]></description>
            <author>miketodd</author>
            <pubDate>Mon, 18 May 2009 19:51:15 +0100</pubDate>
        </item>
        <item>
            <title>How to post to this blog</title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=4&amp;postId=250</link>
            <description><![CDATA[locate the post icon in the header of the blog (on the right), and click on it.<br />
]]></description>
            <author>Franck Martin</author>
            <pubDate>Mon, 18 May 2009 10:35:22 +0100</pubDate>
        </item>
        <item>
            <title>Comments by Timothy Asiedu</title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=3&amp;postId=248</link>
            <description><![CDATA[I believe the fact that we have a created document: “Principles of Affiliation – Operating Framework” is good. This is because this will serve as a reference document for the building of a healthy relation of the various chapters and ISOC global. The document references very important document which are as follows:<br />
<br />
-	 i) ISOC’s Core Principles and Goals<br />
-	ii) ISOC  Chapters  share ISOC’s Core Values<br />
-	iii) ISOC’s Code of Individual Member Conduct..<br />
<br />
This living document will certainly bring about the required transparency and improvement in the relationship of the ISOC Chapters and ISOC Global.<br />
<br />
Let me use this occasion to congratulate the author of this important document in the persons of Anne Lord and Sebastian Ricciardi.<br />
<br />
]]></description>
            <author>tasiedu123</author>
            <pubDate>Fri, 15 May 2009 15:46:23 +0100</pubDate>
        </item>
        <item>
            <title>INPUT SOUGHT: for ISOC response to the US Government Notice of Inquiry on the ICANN Joint ...</title>
            <link>http://wiki.chapters.isoc.org/tiki-view_blog_post.php?blogId=4&amp;postId=247</link>
            <description><![CDATA[DEADLINE FOR COMMENTS: June 8th 2009<br />
<br />
Purpose of consultation:<br />
The United States Department of Commerce has released its notice of inquiry (NOI):  "regarding the upcoming expiration of the JPA with ICANN." This consultation concerns ICANN, its performance and its future.<br />
<br />
ISOC has an important obligation to respond on a matter as critical as this for the future of the Internet and the Internet model as a whole.<br />
<br />
Who is being consulted?<br />
In line with the Society’s mission we are consulting broadly: ISOC Members, Chapter leaders, Board of Trustees, Internet Community and IETF.<br />
<br />
How to participate?<br />
Comment on this blog and/or reply to emails sent to different groups.<br />
<br />
Timelines:<br />
<tt> - May 12: Consultation launched, comments invited.</tt><br />
<tt> - May 18: Board of Trustees discussion of response.</tt><br />
<tt> - May 27: End of comment period. I may need to follow up with some of you for clarification or more information.</tt><br />
<tt> - June 8: ISOC files comments with Department of Commerce, shares final version internally.</tt><br />
<br />
Details:<br />
<br />
The US Government NOI addresses 8 questions:<br />
<br />
1. Is the original White Paper principles are still appropriate?<br />
2. Has ICANN integrated the White Paper principles?<br />
3. Is the private sector-led, bottom-up process is still the most appropriate or are there better models?<br />
4. How is ICANN's progress against the JPA core tasks and subsequent commitments made by the ICANN Board?<br />
5. Is progress sufficient to transition ICANN to full independence, and if not what remains to be done?<br />
6. Are there enough safeguards in place to ensure continued security and stability of the DNS?<br />
7. Can ICANN ensure protection of stakeholder interests and the model itself?<br />
8. What should the NTIA final report on the JPA include?<br />
<br />
Preliminary ideas for ISOC response (including some suggestions in {brackets} where your views are appreciated):<br />
<br />
1. Emphasize the fundamental role of ICANN as a steward of a global resource.<br />
<br />
{It might be something like: ICANN must always remember its fundamental responsibility as the steward over a shared global resource. ICANN is not a simple aggregator of the interests of its multiple constituencies. This central obligation should drive the future direction and activities of the organization. And it implies that the ICANN Board must accept the responsibility to do what is right for the Internet, even if that course is not the most popular with some of its most powerful constituencies.}<br />
<br />
2. Support the original four principles for management of the DNS as having ongoing relevance (those were: stability; competition; private, bottom-up coordination; and representation)<br />
<br />
3. Support the full privatization of ICANN at the end of the JPA to promote private-sector (defined as non-governmental, private) leadership and bottom-up policy making, consistent with our previous statements to the US government.<br />
<br />
4. Draw attention to the ongoing need to improve accountability and transparency mechanisms (ref. the first point), but stress that this is something that the ICANN stakeholders can and must accept responsibility for doing.<br />
<br />
5. Support the identified need to continue to strengthen mechanisms to avoid capture<br />
{Are the current mechanisms are sufficiently strong? Are improvements needed and if so what?}<br />
<br />
6. The US Government emphasizes the requirement that it and ICANN collaborate on a DNS Project Report that will document ICANN's policies and procedures designed and developed pursuant to the agreement. They ask what should be included in this report?<br />
<br />
{This would be a good place to reiterate the stewardship role. Are there other messages ISOC should propose for inclusion in this report?}<br />
<br />
<br />
References:<br />
<br />
Original email on May 12 posted to chapter delegates at:<br />
<a class="wiki"  href="http://elists.isoc.org/pipermail/chapter-delegates/2009-May/004956.html">http://elists.isoc.org/pipermail/chapter-delegates/2009-May/004956.html</a><br />
<br />
Additional information:<br />
<br />
1. ISOC's previous inputs to the US Department of Commerce can be found at:<br />
<a class="wiki"  href="http://www.isoc.org/pubpolpillar/docs/ISOC_NTIA_response_060707.pdf">http://www.isoc.org/pubpolpillar/docs/ISOC_NTIA_response_060707.pdf</a><br />
<a class="wiki"  href="http://www.isoc.org/pubpolpillar/docs/ISOC_NTIA_response_080215.pdf">http://www.isoc.org/pubpolpillar/docs/ISOC_NTIA_response_080215.pdf</a><br />
<br />
2. ISOC's inputs to the ICANN President's Strategy Committee on the issues of Improving Institutional Confidence at:<br />
<a class="wiki"  href="http://www.isoc.org/pubpolpillar/community/icann.shtml">http://www.isoc.org/pubpolpillar/community/icann.shtml</a><br />
<br />
3. United States Government archive of background papers on the DNS project are available at:<br />
<a class="wiki"  href="http://www.ntia.doc.gov/ntiahome/domainname/background.htm">http://www.ntia.doc.gov/ntiahome/domainname/background.htm</a><br />
<br />
]]></description>
            <author>lord</author>
            <pubDate>Thu, 14 May 2009 11:20:40 +0100</pubDate>
        </item>
    </channel>
</rss>
