<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class="">Thanks for the boot-up Martin.</div><div class=""><br class=""></div><div class="">I’m in the middle of organizing another IGF workshop proposal at the moment so I thought I’d flag a couple things. It looks like we have over 30 people in this group, which is great. I don’t know if everyone is equally familiar with how the IGF workshop proposal process works, or how the Multistakeholder Advisory Committee (MAG) evaluates proposals. But it is an increasingly competitive and difficult business, they usually get well over 200 proposals for under 100 workshop slots, so it’s important to maximize the fit with their multiple and increasingly time-consuming guidelines. There are about five documents at the URL Martin shared one could look at in this regard. Bottom line, the proposal needs to be crisp and provocative in content; it needs co-sponsors from other organizations (preferably not civil society); the speakers need to be very multistakeholder and diverse (geo/gender/perspective/etc), and we have to have full contact and other details on them; there needs to be a plan for remote participation; all the roles must be filled, so we need names of people we know will come to Geneva in December; and so on. </div><div class=""><br class=""></div><div class=""> All a reasonably tall order given that the deadline for submission is a week from tomorrow. This being the case, it will be important to reach agreement quickly on things like text so that outreach to potential speakers, co-sponsors etc. can begin in earnest. </div><div class=""><br class=""></div><div class="">I see Martin has indicated on the Google doc the choice of format as 60 minute break out session. I’ve organized workshops at every IGF except last year (including a number of them for NCUC and NCSG) and have never done one of these, I’ve always done 90 minute panels or large roundtables. Maybe first we should talk about the format we want? Also, are we set on security? I suggested it on the list when we were chatting about possibilities, but I’m not sure how easy it will be for us to organize something on security @ ICANN in the time available, what are the overarching questions we want to explore, what kinds of people could we get, etc. So maybe it’d make sense to sort such threshold issues up front?</div><div class=""><br class=""></div><div class="">Best</div><div class=""><br class=""></div><div class="">Bill</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 25, 2017, at 16:28, Martin Pablo Silva Valent <<a href="mailto:mpsilvavalent@gmail.com" class="">mpsilvavalent@GMAIL.COM</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I sent this email wrong on sunday to the igf-team-request@ email. Here goes right, sorry for that.</div><div class=""><br class=""></div>Dear all,<div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Welcome to the email-list that Tapani so thoughtfully created for us to work on the NCSG Global IGF 2017 Workshop Proposal. A few month ago, after a very successful workshop in the Global IGF 2016, we lunched once again the idea to do a workshop for the 2017 IGF, after a few rounds of ideas in discussions we submitted the request to ICANN and they approved our project.At the end of this email I copy the details that outline the idea that we shared with ICANN, originally given by William Drake (a.k.a Bill) in the NCSG list among other good ones. </div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>For those who might be new to the process, we now have to draft and present a Workshop proposal to the MAG in order to get approved and be able to do it in the IGF meeting. Since the deadline to submit is May 3, we thought it would be wise to have our final draft for April 30 (which is end of next week). The time is very tight, but it is what it is.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Here you can visit the terms and basic information for the proposal: <a href="https://www.intgovforum.org/multilingual/content/igf-2017-call-for-workshop-proposals" class="">https://www.intgovforum.org/multilingual/content/igf-2017-call-for-workshop-proposals</a></div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>I created a googledoc with the official template of the proposal we have to submit, I propose we work on it as we move forward: <a href="https://docs.google.com/document/d/10YJE8rT_yXNgtMDONb8tf4GMYMdmCIdcBIN6XOQSwo0/edit?usp=sharing" class="">https://docs.google.com/document/d/10YJE8rT_yXNgtMDONb8tf4GMYMdmCIdcBIN6XOQSwo0/edit?usp=sharing</a></div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>I propose that the we try to channel the edits trough me on this list and just do comments on the google doc to not overwrite things. </div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>What we need to do now:</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span></div><div class=""><b class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>First: </b>Defining the substantive focus more precisely and linking it clearly to ICANN stuff so it’s not redundant with all the other cybersecurity proposals the MAG will be reviewing. </div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span></div><div class=""><b class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Second</b>: Identifying speakers; </div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>So, based on what we already outlined, we need to tackle that <b class="">First</b> task. I encourage you to read the outline below, the form in the google doc and the resources in the IGF web I link above. Once we finish that we can start making a pool of speakers to contact. I will be filling the draft as we move forward and you can comment the doc if you see something wrong or want to propose an answer or writing.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Each day I will try push the work so sorry in advanced if I spam a little this email list, but we only have a few days to draft this out.</div><div class=""><br class=""></div><div class="">Best regards to all,</div><div class=""><br class=""></div><div class="">Martín Silva</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><b class="">Outline of the Workshop Idea:</b></div><div class=""><br class=""><b class="">1)Activity: Please describe your proposed activity in detail<br class=""></b><br class="">A workshop in Internet Governance Forum on cybersecurity and DNS.<br class=""><br class=""></div><div class="">The workshop will look at cybersecurity specifically in relation to DNS, including management interfaces, owner authentication processes, RDS/whois and related problems like domain hijacking, privacy endangerment, spam etc, not from purely technical perspective but also in how they should affect ICANN policy. The idea is that even non-technical people developing policy should acquire an understanding on how and what kind of security issues they should consider when making policy decisions.<br class=""><br class=""></div><b class="">2) Strategic Alignment. Which area of ICANN’s Strategic Plan does this request support?<br class=""></b><br class=""><div class="">Support a healthy, stable and resilient unique identifier ecosystem.<br class=""><br class=""><b class="">3) Demographics. What audience(s), in which geographies, does your request target?</b></div><div class=""><b class=""><br class=""></b>All ICANN regional groups (NCSG has members in more than 100 countries).<br class=""><br class=""><b class="">4) Deliverables. What arethe desired outcomes of your proposed activity?<br class=""></b><br class="">Raised awareness about cybersecurity issues related to DNS and their policy implications; increased engagement in security work; report feeding into ICANN processes as well as other cybersecurity discussions.<br class=""><br class=""></div><div class=""><b class="">5) Metrics. What measurements will you use to determine whether your activity achieves its desired outcomes?<br class=""></b><br class="">Attendance, both onsite and online; increased participation on related working groups in ICANN and elsewhere; outcome document (report) that's useful as input to other fora like IGF Cybersecurity Best Practices forum.</div></div>_______________________________________________<br class="">Igf-team mailing list<br class=""><a href="mailto:Igf-team@lists.ncsg.is" class="">Igf-team@lists.ncsg.is</a><br class="">https://lists.ncsg.is/mailman/listinfo/igf-team<br class=""></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">***********************************************<br class="">William J. Drake<br class="">International Fellow & Lecturer<br class=""> Media Change & Innovation Division, IPMZ<br class=""> University of Zurich, Switzerland<br class=""><a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a> (direct), <a href="mailto:wjdrake@gmail.com" class="">wjdrake@gmail.com</a> (lists),<br class=""> <a href="http://www.williamdrake.org" class="">www.williamdrake.org</a><br class="">************************************************<br class=""></div></div></div></div></div></div></div></div></div>
</div>
<br class=""></div></body></html>