- ispcp - lists.icann.org

Fw: [gnso-improvem-impl-sc] Consensus Call by 08 Jan 2014 on Resubmitting a Motion
by WUKnoben Dec. 17, 2013

Dec. 17, 2013

All, from my point of view the language can be accepted. Please let me know any comments/amendments/questions. Merry Christmas Wolf-Ulrich From: Julie Hedlund Sent: Tuesday, December 17, 2013 10:22 PM To: gnso-improvem-impl-sc(a)icann.org Subject: [gnso-improvem-impl-sc] Consensus Call by 08 Jan 2014 on Resubmitting a Motion Dear SCI members, Note that per the SCI Charter, "Unless otherwise determined by the SCI members, committee decisions will be made by “full consensus” process as described in the GNSO Working Group Guidelines (see section 3.6)." Thus, as agreed at the SCI meeting today, staff is requesting a consensus call on the language provided by Greg Shatan concerning changes to the GNSO Council Operating Procedures on resubmitting a motion. Please see the attached redlined and clean versions of the language. Please review this language in your Constituencies and Stakeholder Groups if you have not already done so. If there are no objections or changes to the language received by Wednesday, 08 January 2014, the language will be presumed to be accepted by full consensus. If the language is approved the next step will be for staff to prepare a redlined version of the GNSO Council Operating Procedures that will be put out for public comment for 21 days. However, as noted on today's call this may be combined with changes to the GNSO Working Group Guidelines relating to the working group self-assessment survey (as being prepared by Ken Bour). Best regards, Julie Julie Hedlund, Policy Director

1 0

[council] Public Comment Period: New gTLD Auction Rules
by Glen de Saint Géry Dec. 17, 2013

Dec. 17, 2013

http://www.icann.org/en/news/announcements/announcement-17dec13-en.htm New gTLD Auction Rules Comment / Reply Periods (*) Comment Open Date: 17 December 2013 Comment Close Date: 14 January 2014 - 23:59 UTC Reply Open Date: 15 January 2014 Reply Close Date: 4 February 2014 - 23:59 UTC Important Information Links Public Comment Announcement To Submit Your Comments (Forum) View Comments Submitted Brief Overview Originating Organization: Global Domains Division Categories/Tags: New gTLD Auctions Purpose (Brief): To gather community input regarding the detailed rules and processes for Auctions to resolve string contention sets in the New gTLD Program. Current Status: The Auction Rules (version 2013.12.12) have been updated since the publication of the Preliminary Auction Rules on 1 Nov 2013 based on community feedback, including feedback received in Webinars and sessions at the ICANN 48 meeting in Buenos Aires. Additionally the Bidder’s Agreement, Bidder forms, and a Draft Auction Schedule have been published for community input. Next Steps: Based on public comment feedback, a final set of Auction Rules and Bidder’s Agreement will be published and New gTLD Auctions to resolve string contention sets will be implemented and executed per the rules. Staff Contact: Russ Weinstein Email Staff Contact Detailed Information Section I: Description, Explanation, and Purpose: ICANN is pleased to announce the publication of an updated version (2013.12.12) of the Auction Rules, the Bidder Agreement, the Bidder Forms, and a Draft Auction Schedule for community review. The Auction Rules have been updated since the initial release of the Preliminary Auction Rules on 1 Nov 2013 based on feedback received including during the Auctions Webinar on 7 November 2013 and the ICANN 48 Meeting in Buenos Aires. The documents being published for comment are: · Auction Rules version 2013.12.12 – provides a detailed insight into all facets of the Auctions program, including eligibility, scheduling considerations, preparation procedures, deposits, bidding limits, bidding procedures, the conclusion of auctions, payments and refunds. This version of the Auction Rules only addresses Contention Sets with direct contention relationships; an update or addendum will be published at later time to address Contention Sets with both direct and indirect contention relationships. · Bidder Forms – allows an applicant to designate itself or another entity to act as the bidder on its behalf. These forms will be used by ICANN and Power Auctions (the Auction Manager) to perform due diligence, set up a bank subaccount and a user account on the Auction Site. The bidder forms must be completed for each application participating in an Auction. · Bidder Agreement – an agreement between the Applicant and/or Bidder and Power Auctions, detailing the roles and responsibilities of each of these parties in the Auction process. The Bidder Agreement must be executed at least one time for each Applicant, and if an applicant utilizes a Designated Bidder, the agreement must be executed for each unique configuration of Applicant and Designated Bidder. · Draft Auction Schedule – Using the preliminary contention sets which do not include the effect any objection determinations may have, a Draft Auction Schedule has been created. This schedule utilizes the scheduling criteria defined in the Auction Rules but, due to the dynamic nature of application status, does not take into account the eligibility requirements for a contention set to be sent to Auction by ICANN as defined in the Applicant Guide Book and the Auction Rules. Should contention sets either resolve prior to their scheduled Auction or not yet be eligible for an Auction, ICANN will adjust the schedule in attempt to maintain approximately 20 contention sets per Auction. ICANN intends to publish a Master Escrow agreement between ICANN, Power Auctions and the Escrow Provider for informational purposes prior to the conclusion of the public comment period. It is not envisioned that Bidders will execute an agreement with the Escrow Provider; rather the Bidder's Agreement will create a relationship where the Bidder will be a third party beneficiary to the Escrow Agreement. The Escrow provider will establish accounts by Bidder to securely hold deposits, issue refunds to Bidders based on the Auction Results, and collect winning fees on behalf of ICANN. All feedback will be taken into account, but community feedback on the following topics will be especially helpful. The pace and schedule of auctions to resolve all outstanding contention sets The duration of auction rounds and recesses between rounds The effects of the Name Collision issues on the eligibility for auction of a contention set With the input from the community in this public comment period, ICANN will complete and publish the Auction Rules, Bidder's Agreement, Bidder Forms and move forward to administer Auctions to resolve string contention sets on the new gTLD program. Section II: Background: Section 4.3 of the Applicant Guidebook describes auctions as the last resort method to resolve string contention sets. This section provides for an Ascending Clock Auction methodology and provides an overview of the process and simplified illustrations of the execution of a contention set auction. On 1 November 2013, a preliminary version of the Auction rules was published. The Auction Rules were published as preliminary because there were several aspects related to scheduling that would benefit from community feedback prior to finalization and execution of the Auction program. The Auction Rules have since been updated to provide more details of the Auction processes and procedures as well as to incorporate community feedback received since the initial publication. Section III: Document and Resource Links: Applicant Guide Book section 4.3 [PDF, 429 KB] New gTLD Auction Rules 2013.12.12 [PDF, 323 KB] New gTLD Auction Rules_1Nov13 [PDF, 235 KB] (Preliminary) Redline of Auction Rules 2013.12.12 to 2013.11.01 [PDF, 352 KB] (Comparison of current version to preliminary) Draft Auction Schedule 2013.12.16 [PDF, 308 KB] New gTLD Auction Bidder Agreement [PDF, 171 KB] New gTLD Auction Bidder Forms [PDF, 241 KB] Section IV: Additional Information: N/A (*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

string delegations
by Mike O'Connor Dec. 14, 2013

Dec. 14, 2013

hi all ANNOUNCEMENT: a major research project aimed at developing tools and techniques to identify and mitigate name-collision risks was announced yesterday by Verisign. i wrote a blog post that describes the name-collision problem and encourages researchers to get involved with that research effort. please promote that project to your colleagues. i've added the link to the "handy links" at the bottom of this note. here are the strings delegated last week DATE STRING REGISTRY 10 December 2013 .RUHR Regiodot GmbH & Co. KG Description of the name-collision problem and link to mitigation research project -- http://www.haven2.com/index.php/archives/name-collision-research ICANN's "Name Collision Resources and Information" page - http://www.icann.org/en/help/name-collision ICANN's list of all delegated new gTLDs - http://newgtlds.icann.org/en/program-status/delegated-strings mikey

1 0

Michele Neylon and Blacknight on name-collision
by Mike O'Connor Dec. 11, 2013

Dec. 11, 2013

hi all, here's an example of an outreach item that we could use as a model. mikey http://www.prweb.com/releases/2013/12/prweb11412696.htm Blacknight Advises IT Professionals to Take Steps to Mitigate Potential Name Collision Issues Leading Irish registrar joins ICANN in public education campaign to promote DNS stability. We want to get the message out to all IT professionals to change these internal names to FQDNs to get ahead of the problem. Carlow,Ireland (PRWEB) December 11, 2013 Leading Irish domain registrar and hosting company, Blacknight joins ICANN in urging IT professionals to correct potential Name Collision issues before they become a critical problem. A report released by ICANN on December 6, 2013, titled “Name Collision Identification and Mitigation for IT Professionals”, explains the nature and causes of name collision and proposes a range of possible solutions. Domain Name Collision happens when a name used by an individual or organisation for their private networks matches a new TLD that has entered the DNS. For instance if a company were using an internal name called “company.printer.office” this unqualified domain could “collide” with the .office TLD and cause network confusion. However, according to ICANN, the report shows that private networks will consistently, stably, and reliably perform name resolution when they use Fully Qualified Domain Names (FQDNs) and resolve them from the global DNS. “The Collision reports on individual new TLDs are staggering,” Blacknight CEO Michele Neylon explains. “In some cases there are thousands of “internal names” and private name spaces causing collision for a single TLD as private query results show up in the global DNS. We want to get the message out to all IT professionals to change these internal names to FQDNs to get ahead of the problem.” To mitigate the problem, ICANN recommends that users not already using FQDNs from the public DNS should consider the following strategy: Monitor name services, compile a list of private TLDs or short unqualified names you use internally, and compare the list you create against the list of new TLD strings. (You can see all applications on http://www.dotwhat.co) Formulate a plan to mitigate causes of leakage. Prepare users for the impending change in name usage by notifying them in advance or providing training Implement your plan to mitigate the potential collision Neylon continues: “If these potential issues go uncorrected, it will become a problem for both the global DNS and internal networks using the names that are causing collision. At Blacknight we pride ourselves on providing our customers with a pain free online experience and will continue to update and educate the community on any related developments to stay far ahead of this problem.” ICANN’s Name Collision resources, including the Name Collision Identification and Mitigation for IT Professionals report can be found at http://www.icann.org/en/help/name-collision. For more information on Blacknight’s suite of services please visit http://www.blacknight.com. About Blacknight: Blacknight are an Irish based, ICANN accredited domain registrar and hosting company. Recipients of several awards for their revolutionary use of social media, Blacknight are one of Europe’s most cutting edge Internet companies. Blacknight constantly seek to lead the way by introducing innovative solutions for its client base and provide dedicated servers and colocation as well as a comprehensive range of Microsoft Windows and Linux based hosting plans and domain name registration services to business globally. PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

FW: ccwg-internet-governance Digest, Vol 1, Issue 19
by Tony Holmes Dec. 11, 2013

Dec. 11, 2013

All Draft Charter for the ccwg Internet Governance is below Tony -------------------------------------------------------------- *Problem Statement* What is the problem to be solved? Prepare for ICANN-community participation in the upcoming meeting in Brazil How does not solving this problem get in the way of achieving the organisation's objectives? The ICANN community might miss opportunities to contribute to the dialog and outcomes of the meeting. Also, not involving the ICANN community in the preparation of this meeting will make it impossible for this to be a community-led, bottom up preparation process. What value does the organization gain from solving this problem? Engage in a bottom-up led conversation to advance the agenda articulated in the Montevideo Statement What is the chronology of the situation - how did we get here? http://www.icann.org/en/news/announcements/announcement-07oct13-en.htmMontev ideo Statement Idea of CCWG floated in the early-morning community meeting at ICANN48 On Thursday, ALAC and NCSG create a working group which the whole ICANN community is invited to join. What alternatives to doing this project have we explored? The alternative is to NOT get involved as a community in the Brazil meeting nor the 1net coordination. This risks having parts of the community involved in an unstructured way thus bringing an imbalance to the input provided by the ICANN community in the 1net process. Stakeholders All Stakeholders at ICANN. Who will be affected by the problem? Absolutely everyone. ICANN's model is at risk. Which employees? ICANN policy staff - from two perspectives: support and policy-input ICANN senior staff - from two perspectives: strategy and goal alignment, and funding/logistics Stakeholders? All ICANN AC/SO's and stakeholders group/constituencies within them may have an interest. Others? Potential for including groups that are not part of ICANN. Suggestion that the different SO/AC/SGs should reach out to their respective communities outside ICANN and let them know this work is taking place, channeling any of their concerns via them as their representative. Have they been involved sufficiently up to this point? There is a sense of being left in the dark that is quite prevalent in the community right now. This effort presents an opportunity to broaden engagement and make the process more transparent. Should they be brought in to the project? When? While there is a small risk of too many voices causing confusion, the posture of this effort is that broad engagement and participation are welcome. Smaller groups can be formed if things become unwieldy example :a kind of pyramidal structure where there will indeed be splinter groups or sub-working groups that will come back to the wider group to report. To what degree do they share the belief that this is a problem that needs to be solved? Broad agreement that the ICANN community needs to participate effectively in the Brazil meeting Who ought to 'champion' this project? As this is a cross-community effort, AC/SO/Constituency leadership should champion To whom should the project team report? Facilitators who will help with the communication of information between the various groups & the Board & Staff. Co-Chairs who will direct the work itself. Do we need a Steering Committee to provide resources and resolve disputes? Yes -- include AC/SO/Constituency chairs and staff leaders (at least one from policy staff and one from senior staff). The goals are speedy formation, infrequent interventions and nimble/helpful response when needed. Scope, Size and Perspective What written definition clearly distinguishes between what is inside this project, and what is outside? In scope: Discuss logistical questions related to attending and participating in the Brazil meeting Identify representatives to attend the meeting Develop mechanisms whereby in-person participants can inform, and obtain guidance from, remote participants during the course of the meeting In scope? start creating position papers & put them on a WIKI & then from these position papers, see what commonality the different writers have. Provide a point of contact between ICANN and the broader 1Net initiative? Out of scope Provide input to the Internet Governance Strategic Panel What is the level of detail and precision involved in this effort - is this a sweeping global effort (like a vision or strategy) or is this a project to produce specific outcomes (like install a system, or build a house)? This is a narrowly-focused effort to prepare the ICANN community for a new meeting that is a few months away. this group should spend most of its time on the content -- certainly not finding answers, but certainly finding the right questions to launch into the debate that will take place in Brazil. Goals & Objectives What tangible, deliverable things do we want to see when this project is completed? To convey message from the ICANN community to Brazil meeting about common positions and also diverse opinions from ICANN groups regarding the issues to be covered by the meeting This project will provide ICANN with clear positions that it will be able to hold at the Brazil Summit thus parrying attacks on the multi-stakeholder model How do we know when the project is done? This effort will conclude shortly after the end of the Brazil meeting Critical Success Factors What things do we need to do well in order for this project to succeed? Remain focused on the narrow scope of preparing for Brazil Try to put aside historic rivalries and mistrust Focus more on the message and less on positions/logistics/politics. Work to a short-interval schedule Focus the work on email lists, wikis and other asynchronous tools. Use periodic teleconferences sparingly and wisely Build relationships and trust, both inside and outside of ICANN Preferred Problem-Solving Approach These questions are the socket into which a work plan is inserted. Revisit them once the broad outlines of the charter are agreed. Who will do what tasks, with whom, by what date? What are the intermediate milestone events and deliverables that we can use as checkpoints to monitor the progress of the project? Are they more than 1 or 2 weeks apart? Do we need more (or fewer) tasks and milestones to keep the project under a reasonable level of control? What's the mechanism for getting things back on track if the project is missing key dates? setting a roadmap Write a comment...

1 0

Reminder: ICANN WHOIS MISUSE STUDY FINDINGS WEBINAR INVITATION
by Tony Holmes Dec. 10, 2013

Dec. 10, 2013

To ISPCP members FYI Please respond directly to the invitation if you plan to join the webinar From: owner-liaison6c(a)gnso.icann.org [mailto:owner-liaison6c@gnso.icann.org] On Behalf Of Glen de Saint Géry Sent: 10 December 2013 17:01 To: liaison6c Subject: [liaison6c] Reminder: ICANN WHOIS MISUSE STUDY FINDINGS WEBINAR INVITATION ICANN WHOIS MISUSE STUDY FINDINGS WEBINAR INVITATION  In order to participate, please RSVP via email to the GNSO Secretariat ( <mailto:gnso.secretariat@gnso.icann.org> gnso.secretariat(a)gnso.icann.org) to receive the call details. You are invited to participate in a webinar about the recently released Whois Misuse Study, conducted for ICANN by Carnegie Mellon University’s Cylab. This study has now been published for public comment, and community feedback is being invited in order to assist ICANN with evaluating potential changes to Whois policy. The study was commissioned by the GNSO to obtain objective and quantifiable information about the extent, nature, and impact of WHOIS public data misuse – that is, harmful actions taken using contact information obtained from WHOIS – through (1) analyzing reported misuse incidents and (2) conducting experiments to measure misuse and the effectiveness of anti-harvesting measures. CMU was engaged to perform the study using two complementary approaches: (1) a descriptive study to document and analyze WHOIS misuse incidents that have already occurred and (2) an experimental study to stimulate and record misuse in order to measure more reliably the impact of making WHOIS data public and WHOIS query filters applied to deter data harvesting. CMU’s chief researchers on the study, Dr. Nicolas Christin and Mr. Nektarios Leontiadis, and ICANN staff will provide a briefing on Tuesday 17 December at 12.00 UTC and 19.00 UTC, summarizing their findings and conclusions based on the studies they performed and data they analyzed. Amongst other topics, Dr. Christin and Mr. Nektarios will discuss: · CMU’s methodology for the study and the hypothesis tested; · The different project activities that were undertaken for the study; · CMU’s analysis of the data reported and sampled for the study; and · CMU’s conclusions based on the results of its analysis. The two sessions are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for sixty (60) minutes, will be conducted in English only. The meeting will be run in Adobe Connect with a slide presentation along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may also be submitted using the chat function of Adobe Connect. If you are not able to participate in either of the live sessions, the recording of the session will be made available shortly after the meeting. The policy staff is always available to answer any questions that you email to <mailto:policy-staff@icann.org> policy-staff(a)icann.org. In order to participate, please RSVP via email to the GNSO Secretariat ( <mailto:gnso.secretariat@gnso.icann.org> gnso.secretariat(a)gnso.icann.org) to receive the call details. Please indicate which call you would like to join on Tuesday 17 December - at 12.00 UTC or at 19.00 UTC (to convert those times into your local time, see: <http://www.timeanddate.com/worldclock/fixedform.html> http://www.timeanddate.com/worldclock/fixedform.html) We will send you an e-mail reminder before the event with log-in and dial-in details. Please DO NOT RSVP to any other ICANN staff member’s e-mail address.

1 0

Fwd: WEBINAR CANCELLATION: TRANSLATION AND TRANSLITERATION OF CONTACT INFORMATION
by Mike O'Connor Dec. 9, 2013

Dec. 9, 2013

> > *********************************************************************************************************** > > > Dear all, > > Due to a very low number of sign-ups we have decided to cancel the Introductory Webinar on Translation and Transliteration of Contact Information. > If you are interested in the subject, please note that you can join the Working Group at any time by contacting gnso-secs(a)icann.org. > > The first meeting of the Working Group will be held in the week of 16 December 2013 and staff will provide an introductory presentation based on the (now cancelled) Webinar to familiarize volunteers with the subject at hand. > > Many thanks and best wishes > > Kind regards, > > Nathalie > GNSO Secretariat PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

1 0

string delegations
by Mike O'Connor Dec. 7, 2013

Dec. 7, 2013

hi all here are the strings delegated last week DATE STRING REGISTRY 30 November 2013 .MENU Wedding TLD2, LLC 30 November 2013 .UNO Dot Latin, LLC 23 November 2013 みんな (xn--q9jyb4c) - Japanese for "everyone" Charleston Road Registry, Inc. ICANN's "Name Collision Resources and Information" page - http://www.icann.org/en/help/name-collision ICANN's list of all delegated new gTLDs - http://newgtlds.icann.org/en/program-status/delegated-strings mikey

1 0

FW: GNSO Web-Site Survey
by Tony Holmes Dec. 6, 2013

Dec. 6, 2013

FYI and action From: Glen de Saint Géry [mailto:Glen@icann.org] Sent: 04 December 2013 18:32 To: tony holmes (tonyarholmes(a)btinternet.com) Mike O'Connor Subject: GNSO Web-Site Survey Please distribute this to all your members. Thank you very much. Glen GNSO Web-Site Survey http://gnso.icann.org/en/announcements/announcement-04dec13-en.htm 4 December 2013 In May of 2012, the GNSO Policy Team, in partnership with ICANN's Web Team, launched a new theme and information structure for the GNSO website. The primary goal of that initiative was to improve the information architecture of the web site and to better align the documentation of GNSO Council activities with other community operations on the site. Key new features included: * More clarity regarding the activities of the GNSO community, the GNSO Council and its Working Groups * Quick access to active projects and an archive of past GNSO Council efforts * Better descriptions of the current GNSO organizational structures including archives of its various structures from the formative years of the GNSO as it transitioned from the DNSO (note, documentation of past efforts is still under way) * Web site integration with myICANN for pushing (RSS) change notifications So far, the site has experienced nearly 26,000 visits (130/day on avg.) with just over 15,000 being unique visitors. On average, users tend to visit 2.5 pages -- for an average duration of nearly three minutes. Approximately 30% of the traffic is from outside the United States. While we've been collecting a good bit of data about how often the improved site is visited (e.g., Google analytics, etc.), we now want to gather direct community feedback from you on how effective the site is proving to be, so that we can determine what further improvements are desirable and achievable. We've developed the following survey to provide a structured method to collect your input. The survey is designed to take no longer than ten minutes to complete even if you choose to expand your responses with additional text which we hope you'll do!. After the survey closes in December, we will collate and analyze the results and publish a report for GNSO leadership review. Depending on the feedback collected, that report may include recommendations for future enhancement. If you are interested in being contacted by us for further discussion and/or feedback regarding your survey responses, please email the GNSO Policy Team at <mailto:policy-staff@icann.org> policy-staff(a)icann.org. Please follow this link for the survey: <https://www.surveymonkey.com/s/3WBSFFK> https://www.surveymonkey.com/s/3WBSFFK The Survey closes on 10 January 2014 @ 23:59 UTC. Thanks very much for taking the time to give your feedback. We look forward to reading your views and learning from your experiences with the site. Best regards, The GNSO Policy Team Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

FW: MSI Panel: A Call to Action
by Tony Holmes Dec. 4, 2013

Dec. 4, 2013

FYI <https://gallery.mailchimp.com/1a990feb5c/images/logo_icann_ideascale_3_.png > Designing a 21st Century ICANN Hello! The <http://www.icann.org/en/about/planning/strategic-engagement/multistakeholde r-innovation> ICANN Strategy Panel on Multistakeholder Innovation (the MSI Panel) and <http://thegovlab.org/> The Governance Lab @ NYU (The GovLab) recently launched an online engagement effort aimed at helping to design a 21st century Internet Corporation for Assigned Names and Numbers (ICANN) - the public interest organization responsible for coordinating the Internet's Domain Name System (DNS). We are writing to request your participation in this important initiative and to help us spread the word! The MSI Panel has been charged with: . Proposing new models for international engagement, consensus-driven policymaking and institutional structures to support such enhanced functions; and . Designing processes, tools and platforms that enable the global ICANN community to engage in these new forms of participatory decision-making. The Panel is a small group of seven with no monopoly on the best ideas for what ICANN should or should not do to coordinate the DNS in the public interest. All suggestions to make ICANN more effective and more democratic - whether constitutional, structural, legal, procedural or technological - will be welcome. While we cannot decide for ICANN, the aim of the MSI Panel is to use its authority to push for real change. Thus, we want ideas that are concrete and specific for innovative processes, structures, platforms, and techniques to design a 21st century ICANN. To gather and organize your input - we're launching this campaign in three stages: Stage 1: Idea Generation - Starting November 19th and running for six weeks via an ideation platform, Ideascale. You can access our <http://bit.ly/1dS9sLp> MSI Panel community page here. On the page, you can submit any and all concrete ideas you have. You can rate and rank others' for importance and practicality. November 19 - December 31. Stage 2: Proposal Development - Submissions will be grouped into general proposals and opened to discussion using a blog with line-by-line annotation features. This phase will be designed to take ideas closer to implementation. January 14 - January 21. Stage 3: Collaborative Drafting - Using a wiki, we will invite collaborative drafting on specific proposals that the Panel will submit to the ICANN CEO, Board and community. January 28 - February 11. To help us spread the word, we ask you to do any of the following: . Submit ideas and encourage members of your network/community to contribute to the Ideascale community site by providing them with the link: <http://thegovlab.ideascale.com/> http://thegovlab.ideascale.com/. . Broadcast our "Call To Action," for this initiative, which is online <http://bit.ly/HWNxrW> here, as widely as possible within your networks. Feel free to link to this post or repost on your website edited to fit your needs. . Share this information within your community and network via mailing lists and listservs. . Use social media platforms such as Facebook or Twitter to spread the word about the campaign. Don't forget to use the hashtag #WeCANN. . To inspire participation and learn how to contribute, watch and share a <http://bit.ly/185t28Q> video The GovLab has made for the launch of this distributed brainstorm. . Host your own brainstorming forum and share ideas generated with the MSI Panel on our Ideascale community page. For more information, visit The GovLab at <http://www.thegovlab.org/> www.thegovlab.org. Thanks and best, The MSI Panel & The GovLab

1 0