<div dir="ltr"><div class="gmail_extra">Hi Joao,</div><div class="gmail_extra"><br>
<br><div class="gmail_quote">2015-12-29 5:13 GMT+09:00 João Carlos Rebello Caribé <span dir="ltr"><<a href="mailto:caribe@entropia.blog.br" target="_blank">caribe@entropia.blog.br</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Rafik and other EC members, I reiterate my candidacy as representative of the NCUC to this CS project, had already come into contact with Adam, soon after the meeting of Dublin, offering to join the project team. I believe I have strong experience on this issue to do a good job.<div><br></div></div></blockquote><div>my understanding from Adam is there is no one rep per se but a group for coordination (a specific mailing list to be created as shared during the last webinar)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div><div>I suggest a simple task to solve this input:</div><div><br></div><div>We need to map the main characteristic of any of this: At-Large, NPOC and NCUC (GROUPS)</div><div><br></div><div>What are the main similarities and differences of these GROUPS on:</div><div> 1) Participation at ICANN ecosystem. </div></div></blockquote><div><br></div><div>ALAC is an advisory committee (providing advices to board) covering broader range of topics regarding numbering and addressing. having broad range of topics may confuse people since many may think that ALAC can cover all-things internet with many not within ICANN remit</div><div>while we are focusing in gTLD policies and currently on ICANN structure and accountability because the iana transition process . we can provide concrete examples as we did in several NCUC outreach session in ICANN meetings</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div> 2) Engagement needs (E.G. NCUC accept individuals, At-Large just NGOs, etc)</div><div><br></div></div></blockquote><div>NCUC accepts individuals and non-commercial organizations (NFP, NGO, associations, foundations, advocacy group, universities etc) </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div><div>This map would support to answer simple questions of potential candidates, e.g. </div><div> How you plan to participate in ICANN? </div><div> a) Building polices of gTLD, IP and other GNSO ISSUES >> GNSO</div><div><br></div><div> On GNSO what are your focus in human rights? Operational procedures or Human rights at all ? >> NPOC or NCUC </div><div><br></div></div></blockquote><div> </div><div>NCUC is not just about Human Rights, but rights of registrants and users in general. also we need to be careful to not entertain the myth that NCUC is only for individual users. we are quite open and our criteria about having non-commercial interests.</div><div><br></div><div>for example we covered issues related to new gTLD program because it would have impact on registrants in general .</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div><div>We can work better mapping the similarities and differences of these GROUPS.</div><div><br></div><div>At-Large does a great job on this issues, their slides and folders are very easy and instructive for newcomers.</div><div><br></div></div></blockquote><div><br></div><div>I would prefer avoiding comparison against ALAC, we don't have the same nature, staffing and mission . let's focus on our work while learning from other best practices. yes we can create similar material but it means that we have to work on that by ourselves. the ICANN CS strategy includes some support but up to us to create the content and substance. for example we have our website which can be revamped but also needs more content such as blog posts and briefs.</div><div>it will be useful to have some slide deck when can use for outreach presentations.</div><div><br></div><div>for reminder, we can have additional print-out for marrakech meeting in addition to the flyer ( edited by Farzaneh)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div><div>Finally we need to improve our NCUC communication strategy, will send suggestions early on January.</div><div><br></div></div></blockquote><div><br></div><div>Thanks, looking forward to get the plan.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><div><div><br><div><div><div class="h5"><div>Em 28/12/2015, às 12:36, Rafik Dammak escreveu:</div><br></div></div><blockquote type="cite"><div><div class="h5"><div dir="ltr">Hi there,<div><br></div><div>this was sent by Adam and he is asking for input here.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Adam Peake</b> <span dir="ltr"><<a href="mailto:adam.peake@icann.org" target="_blank">adam.peake@icann.org</a>></span><br>Date: 2015-12-24 1:50 GMT+09:00<br>Subject: civil society in ICANN - description<br>To: Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>>, Tapani Tarvainen <<a href="mailto:tapani.tarvainen@effi.org" target="_blank">tapani.tarvainen@effi.org</a>>, "Rudi Vansnick (NPOC)" <<a href="mailto:rudi.vansnick@npoc.org" target="_blank">rudi.vansnick@npoc.org</a>>, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>><br>Cc: Heidi Ullrich <<a href="mailto:Heidi.Ullrich@icann.org" target="_blank">Heidi.Ullrich@icann.org</a>><br><br><br>
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:16px;font-family:Calibri,sans-serif">
<div>
<div>Dear Alan, Rafik, Rudi, Tapani:</div>
<div><br>
</div>
<div>You have probably heard me say that one of the things we want the CS strategy to address is a problem many newcomers mention: that they are unsure about which group is their natural home in ICANN. We hear comments from Fellows and NextGen participants
at the end of ICANN meetings saying they don't know whether they should be joining At-Large, NCUC or NPOC. And it can be quite difficult to persuade an audience at a general outreach event of the differences. </div>
<div><br>
</div>
<div>I hope we can clarify the distinctions between your different missions. </div>
<div><br>
</div>
<div>We are working on some new slides. XPLANE can be effective at capturing this sort of thing. </div>
<div><br>
</div>
<div>I would also like your help with some new written material. I've collated text from various community documents describing CS in ICANN. You can find this attached. Editorial has been minimal, most should be text already agreed by the community. Perhaps
in the New Year we could start refining and simplifying this, with the goal of finalizing while together in Marrakech. </div>
<div><br>
</div>
<div>A first version of the XPLANE graphics will be available before Marrakech, but they can also be finalized when we meet. Could you share this document and email with whoever in your communities you think may be interested in helping.</div>
<div><br>
</div>
<div>Warm regards and best wishes,</div>
<div><br>
</div>
<div>Adam</div>
</div>
<div><br>
</div>
</div>
</div><br></div></div>
</div></div><span><CS in ICANN outline.docx></span>_______________________________________________<br>NCUC-EC mailing list<br><a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a><br><a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" target="_blank">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br></blockquote></div><br><div>
--<br>João Carlos R. Caribé<br>Consultor <br>Skype joaocaribe<br>(021) 9 8761 1967
</div>
<br></div></div></div></div></div></blockquote></div><br></div></div>