<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 25 Mar 2014, at 3:03 pm, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">> Our community — the community of people interest in and affected by Internet governance decisions — is numerous and distributed around the globe. It’s unrealistic to think that input can be gathered inclusively through physical meetings. </p><p dir="ltr"><br>
Yes I agree and budget wise it's also unrealistic and I believe others know this. However, for me I think the ground for which the few physical meeting happen is more important. ICANN was mandated to coordinate this process, however it should not solely do this within it's structure. So while ICANN discuss this issues within it's community events (since ICANN community can be seen as a stakeholder) it should organise physical meeting(1 or 2) on a neutral ground where all stakeholders (including outside ICANN) come in to discuss their views and that is where an outcome should be determined.<br>
</p></blockquote><div><br></div><div>Or, it seems obvious, take advantage of other existing meetings where other such stakeholders are likely to be found, including the IGF, the WSIS+10 high level meeting, the World Social Forum, the Chaos Communication Congress...</div><br></div><div>Otherwise I agree with Seun and Ian.</div><br><div apple-content-edited="true">
<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;"><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;"><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;"><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div style="font-size: 12px; text-align: -webkit-auto; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>--</div><div>Jeremy Malcolm PhD LLB (Hons) B Com</div><div>Internet lawyer, ICT policy advocate, geek</div><div>host -t NAPTR 5.9.8.5.2.8.2.2.1.0.6.<a href="http://e164.org">e164.org</a>|awk -F! '{print $3}'</div></div></span><br class="Apple-interchange-newline"></div>WARNING: This email has not been encrypted. You are strongly recommended to enable encryption at your end. For instructions, see <a href="http://jere.my/l/pgp">http://jere.my/l/pgp</a>.</span></div></div></div></div></div>
</div>
<br></body></html>