<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;"><span style="font-family: 'Verdana'; font-size: 10pt; color: rgb(102, 102, 102);">León,<div><br></div><div>Thanks! </div><div><br></div><div>I appreciate that each SO/AC could set its own controls over its ‘alter ego’ and so the question would be more how will any control mechanisms be enforced.</div><div><br></div><div>However, I imagine that it may also be important to each SO/AC to ensure that their fellow SOs and ACs have robust control mechanisms in place.</div><div><br></div><div><div apple-content-edited="true">
<p class="p1"><br></p>
<p class="p2">Cheers,</p>
<p class="p3"><br></p>
<p class="p2">Chris</p>
</div>
<br><div><div>On 30 Apr 2015, at 10:26 , León Felipe Sánchez Ambía <<a href="mailto:leonfelipe@sanchez.mx">leonfelipe@sanchez.mx</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Chris,<div class=""><br class=""></div><div class="">My understanding is that each UA will set its own procedures and conditions. Therefore, control mechanisms should be established by and within each UA. I believe, however, that this is a question worth asking to the lawyers for further clarity so I am forwarding this thread to the legal sub-team list in order to have the lawyers look at the conversation and have their advice on this las point you mention.</div><div class=""><br class=""></div><div class="">Holly and Rosemary,</div><div class=""><br class=""></div><div class="">Is my understanding accurate? As Chris says, which control mechanisms could be put in place and how would they be enforced under the hypothesis discussed in this thread?</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div class="">Best regards,</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">León</div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">El 29/04/2015, a las 18:38, Chris Disspain <<a href="mailto:ceo@auda.org.au" class="">ceo@auda.org.au</a>> escribió:</div><br class="Apple-interchange-newline"><div class=""><span style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; font-family: Verdana; font-size: 10pt; color: rgb(102, 102, 102);" class="">Thanks Greg. Clear and understood.<div class=""><br class=""></div><div class="">What will the control mechanisms be between the ccNSO and its alter ego and how will they be enforced?<br class=""><div class=""><br class=""></div><div class=""><br class=""><div class=""><div style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-family: Helvetica; min-height: 14px;" class=""><br class=""></div><div style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-family: Helvetica; min-height: 14px;" class=""><br class=""></div><div style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; color: rgb(148, 67, 251);" class="">Cheers,</div><div style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; color: rgb(148, 67, 251); min-height: 16px;" class=""><br class=""></div><div style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; color: rgb(148, 67, 251);" class="">Chris</div></div><br class=""><div class=""><div class="">On 30 Apr 2015, at 09:28 , Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" class="">gregshatanipc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family: verdana, sans-serif;">Chris,</div><div class="gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="gmail_default" style="font-family: verdana, sans-serif;">Please let me try to clarify my understanding of what is currently being proposed (in draft). The SO/ACs will not be "converted" into legal entities. Rather, a "mirror" or "alter ego" entity will be set up for each SO/AC, likely as a unincorporated association (which is a recognized legal entity under California law). Each SO/AC will control its alter ego. This is quite similar to the relationship between the ASO and the NRO. The SO/ACs will continue to exist and will perform and operate as they currently do. The legal entities will be the members (or designators, should that route be chosen) of ICANN, with the specific rights and powers ascribed to them in that capacity by statute and bylaw. </div><div class="gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="gmail_default" style="font-family: verdana, sans-serif;">Technically, the unincorporated associations only need a minimum of two members, so any "members" of a SO/AC who don't wish to be members of the alter ego won't need to be. The control arrangements between the SO/AC and the alter ego will ensure that all "members" of the SO/AC (and even non-members, such as non-ccNSO ccTLDs, if desired) get the appropriate "say" in any decisions that are to be carried out by the alter ego.</div><div class="gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="gmail_default" style="font-family: verdana, sans-serif;">Best regards,</div><div class="gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="gmail_default" style="font-family: verdana, sans-serif;">Greg</div><div class="gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Apr 29, 2015 at 6:40 PM, Chris Disspain<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:ceo@auda.org.au" target="_blank" class="">ceo@auda.org.au</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class="">Jordan,<div class=""><br class=""></div><div class="">Apologies for taking so long to respond!</div><span class=""><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">Nobody is proposing converting the SOs and ACs to anything - at all - anywhere.</div></div></div></blockquote><br class=""></div></span><div class="">I’m confused. Greg seems o think that’s exactly what was being proposed. Do we have clarity on this yet?</div><div class=""><br class=""></div><div class="">I’ll respond to the balance of your points later today.<br class=""><div class=""><p class=""><br class=""></p><p class=""><br class=""></p><p class="">Cheers,</p><p class=""><br class=""></p><p class="">Chris</p></div><br class=""><div class=""><div class=""><div class="h5"><div class="">On 22 Apr 2015, at 16:02 , Jordan Carter <<a href="mailto:jordan@internetnz.net.nz" target="_blank" class="">jordan@internetnz.net.nz</a>> wrote:</div><br class=""></div></div><blockquote type="cite" class=""><div class=""><div class="h5"><div dir="ltr" class="">Hi all, hi Chris:<br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On 22 April 2015 at 11:07, Chris Disspain<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:ceo@auda.org.au" target="_blank" class="">ceo@auda.org.au</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class=""><p class="MsoNormal"><span lang="EN-GB" class=""><font color="#444444" class="">Hi Keith,<u class=""></u><u class=""></u></font></span></p><p class="MsoNormal"><font color="#444444" class="">As promised I set out in brief below some of the reasons why, in respect to the membership model and any model requiring the SOs and ACs to convert to legal entities, I have serious concerns and why I referred to significant sacrifices.</font></p></span></div></blockquote><div class=""><br class=""></div><div class="">Nobody is proposing converting the SOs and ACs to anything - at all - anywhere.</div><div class=""><br class=""></div><div class="">The only proposal that I've seen from the lawyers is that if membership was the model chosen, legal personality would need to be created. The actors in the various SOs and ACs would, in exercising membership prerogatives, act through the unincorporated associations.</div><div class=""><br class=""></div><div class="">The lawyers have also been clear that even in a designator model, it's preferable to create legal personality along those lines.</div><div class=""><br class=""></div><div class="">I think it is really really really important for everyone involved in this effort to be very precise and clear about what we are discussing and what we aren't. So I am writing this so directly in order that if my understanding is wrong, it gets picked up pronto! :-)</div><div class=""><br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class=""><p class="MsoNormal"><font color="#444444" class="">GAC</font></p><p class="MsoNormal"><span lang="EN-GB" class=""><font color="#444444" class="">The current recommended model does not provide any viable solution for dealing with the GAC. It seems obvious to me that the governments involved in the GAC are not going to agree to form an unincorporated association under Californian law. If I'm right then presumably the GAC would remain as an advisory committee and would not be able to have a vote in any of the escalation mechanisms. That may be fine as the GAC may not want to have a vote anyway.</font></span></p></span></div></blockquote><div class=""><br class=""></div><div class="">Indeed it may not. Being able to offer advice on public policy issues to the ICANN Board and to appoint a non-voting liaison member to the Board. I am looking forward to hearing their views on this (and many other questions).</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class=""><p class="MsoNormal"><span lang="EN-GB" class=""><font color="#444444" class=""><u class=""></u><u class=""></u></font></span></p><p class="MsoNormal"><font color="#444444" class="">However I see a serious incompatibility between the members’ powers and the standing of GAC advice to the Board. It’s not that GAC advice is or indeed should be invariably followed but currently where GAC advice is at odds with the position of others in the community the advice carries significant weight and there is a bylaw mandated process for rejecting the advice through a process which takes around 6 months. The change to a members based structure would mean that for certain issues the actions of members will trump GAC advice. So there is a significant shift in the carefully constructed balance of power. Now, many of us may think that such a shift is no bad thing but I wonder whether the governments of the world are going to agree?</font></p></span></div></blockquote><div class=""><br class=""></div><div class="">I don't understand this. I have not seen any hint of anyone suggesting that a power that Members should have includes overriding decisions on matters of public policy, which is the advice that the GAC gives the Board and which the bylaws would continue to require it to give due deference to (perhaps with an adjustment about when that reconciliation process has to happen, should GAC change its operating principles).</div><div class=""><br class=""></div><div class="">If GAC advice on public policy matters led to changes in the bylaws, or the inclusion by the Board of business or strategic plans or budgets, then the new powers might have an impact. But all that would require the Board and the GAC to do is to persuade the broader ICANN system, or at least some of it, that their ideas are ones that should be pursued.</div><div class=""><br class=""></div><div class="">Does that feel like a fundamental issue to you? It doesn't to me.</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class=""><p class="MsoNormal"><a name="14d0758631f0807e_14cde3f7179f116a_OLE_LINK1" class=""><span lang="EN-GB" class=""><font color="#444444" class="">ccTLDs</font></span></a></p><p class="MsoNormal"><span lang="EN-GB" class=""><font color="#444444" class="">When we set up the ccNSO and when we did the structural review of it some time thereafter there was considerable discussion about how it could be structured precisely to avoid the need for ccTLDs to join anything. There was even significant concern about having to fill out a form and whether that implied the existence of some organisation. The concerns included joining something in the jurisdiction of the US and whether that would make a ccTLD manager in any way subject to US law, the possibility of being sued in the US because the manager would be deemed to have a presence there, how such a structure would be funded (especially if it was sued), whether there was any liability on ‘officers’ of the entity and so on. I believe that many of these concerns will still exist for many ccTLDs.</font></span></p></span></div></blockquote><div class=""><br class=""></div><div class="">They may or may not. But in that fifteen-years-ago debate, were there any facts on the table about those questions? Or was it all a bit of a mess on many fronts? Because ICANN in 2015 is, better or worse, a very different beast to ICANN in ~ 2000. </div><div class=""><br class="">Perhaps more importantly, exercising some rights through an unincorporated association would remain a choice for every ICANN participant. Nobody would be forced to be involved. It isn't like a "Join ICANN and have no say" - all the current structures for the "business of the business" would remain in place.</div><div class=""><br class=""></div><div class="">From the legends I have heard about this early phase in ICANN's history, the fundamental concern was of a power-grab on the corporation's part. Since these reforms make such a power-grab harder (and let's remember that the end of the NTIA contract makes it easier...), I'd expect ccTLDs and others to look at them with quite some interest.</div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class=""><p class="MsoNormal"><span lang="EN-GB" class=""><font color="#444444" class=""><u class=""></u><u class=""></u></font></span></p><p class="MsoNormal"><font color="#444444" class="">Further, quite a number of ccTLD managers are departments of the relevant government or quasi-government bodies. Not everyone runs their ccTLD with the degree of freedom that .au, .ca, .uk and .nl are privileged to enjoy. I consider it highly unlikely that sovereign governments will permit a government department to join an association in the US (or any other country for that matter).</font></p></span></div></blockquote><div class=""><br class=""></div><div class="">They won't have to, to do what they do in ICANN today.</div><div class=""><br class=""></div><div class="">The suggestion is they might have to if they want to take part in exercising the accountability powers set out in our report that's going for public comment.</div><div class=""><br class=""></div><div class="">That said, there's a bit of an objective legal question here - which is whether the decisions of these uninc associations can be forced to take account of the views expressed in the ICANN bodies they shadow in making their decisions. If they can (which I would analogise to the ccNSO taking on board the views of non-member ccTLDs - and so I assume it is possible), much of this debate becomes moot.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Finally -- I do think this is a really useful and constructive discussion. As someone who is warm to the member approach, but who sees huge benefits if we can manage a "no structural change" outcome, this is just the convo we need to have.</div><div class=""><br class=""></div><div class="">cheers,</div><div class="">Jordan</div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class=""><p class="MsoNormal"><font color="#444444" class="">At Large</font></p><p class="MsoNormal"><span lang="EN-GB" class=""><font color="#444444" class="">I don’t know the answer to this but it strikes me that the structure may also be problematic for At Large community as opposed to ALAC. On that one over the ALAC folks to comment.<u class=""></u><u class=""></u></font></span></p><p class="MsoNormal"><font color="#444444" class="">There’s more but I'm rushing for my flight now. Hope this gives you a flavour.</font></p><div class=""><p class=""><font color="#444444" class=""><br class=""></font></p><p class=""><br class=""></p><p class="">Cheers,</p><p class=""><br class=""></p><p class="">Chris</p></div><div class=""><br class=""><div class=""><div class="">On 21 Apr 2015, at 20:46 , Chris Disspain <<a href="mailto:ceo@auda.org.au" target="_blank" class="">ceo@auda.org.au</a>> wrote:</div><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">Hi Keith,</span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class=""><br class=""></span></div><div class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">Thanks for the below. You ask a valid question and Kavouss has sent me an email asking the same. I will respond in detail in the next 7 hours or so. </span><br class=""><br class="">Chris Disspain<div class="">CEO - auDA</div></div><div class=""><br class="">On 21 Apr 2015, at 20:16, Drazek, Keith <<a href="mailto:kdrazek@verisign.com" target="_blank" class="">kdrazek@verisign.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><span class=""></span></div><div class=""><div class="">Thanks Chris, no apologies necessary...this is exactly the kind of dialogue needed to advance our work. </div><div class=""><br class=""></div><div class="">Can you be more explicit about the "<span style="background-color: rgba(255, 255, 255, 0);" class="">significant number of sacrifices that would need to be made in a membership scenario" that ccTLDs face? Particularly if any are unique to ccTLDs? </span></div><div class=""><br class=""></div><div class="">Sacrifices may be needed (including from the Board) if we are to accomplish the community's broader goal of ensuring the ICANN Board and Staff are truly accountable to the ICANN community for the next decade. As such, it would be good to know, as early as possible, what those sacrifices might be. </div><div class=""><br class=""></div><div class="">In simple terms, I agree that determining what can and cannot be accomplished within the existing structure is a worthwhile exercise and will help to inform the community. </div><div class=""><br class=""></div><div class="">Based on our work and the relevant independent legal analysis to date, it appears to me that the current construct has significant gaps and shortcomings and won't deliver on our goals, but I support seeking further advice on the topic from our independent legal advisors.</div><div class=""><br class=""></div><div class="">Thanks and regards,</div><div class="">Keith</div><div class=""><br class="">On Apr 21, 2015, at 5:08 AM, Chris Disspain <<a href="mailto:ceo@auda.org.au" target="_blank" class="">ceo@auda.org.au</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">Thanks Keith. </div><div class=""><br class=""></div><div class="">I apologise for pinging back and forth on this but I hope the list will appreciate that it as an indication of how important auDA believes this point is. </div><div class=""><br class=""></div><div class="">As I said on the CCWG call last week, I have serious concerns about the viability of the lawyers' recommended structural changes (at least from a cc point of view) and want to be crystal clear about what we can do or cannot do within the current structure.</div><div class=""><br class=""></div><div class="">For a ccTLD there are a significant number of sacrifices that would need to be made in a membership scenario and I don't believe the cc community can decide whether those sacrifices are worth making unless we can weigh them against what we would be able to achieve using the current structure. </div><div class=""><br class=""></div><div class="">I think that is essential that our output to the community contains a clear explanation of what the status quo can achieve. If it does not then IMO it is impossible to judge the other scenarios. </div><div class=""><br class=""></div><div class="">I appreciate your second para and, as a lawyer, I know that time for a response is required. I also appreciate the time constraints under which we are operating. But we will lose more time if the result of our document is a series of questions about whether there really is a need to make the significant changes being recommended. </div><div class=""><br class=""></div><div class="">In simple terms 'not nearly enough' is not an acceptable response. How can I know that "it" is not nearly enough unless I know what "it" is?</div><div class=""><br class=""></div><div class="">Chris Disspain<div class="">CEO - auDA</div></div><div class=""><br class="">On 21 Apr 2015, at 18:37, Drazek, Keith <<a href="mailto:kdrazek@verisign.com" target="_blank" class="">kdrazek@verisign.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class=""><br class=""></div><div class="">Chris, </div><div class=""><br class=""></div><div class="">I believe the answer to your question regarding the "no change scenario" and "what the current configuration can achieve" is, "Not nearly enough." </div><div class=""><br class=""></div><div class="">That said, I think it's a reasonable question and it should be referred to the CCWG's lawyers and they should be permitted reasonable time to consider and respond.</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Keith</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class="">Sent from my iPhone</div><div class=""><br class="">On Apr 21, 2015, at 4:09 AM, Chris Disspain <<a href="mailto:ceo@auda.org.au" target="_blank" class="">ceo@auda.org.au</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">Greg,</div><div class=""><br class=""></div><div class="">Thanks. At the risk of repeating myself, whilst I understand what you are saying, it is precisely the no change scenario that I am seeking clarity on. I accept that the current configuration may not be "a very good vehicle for many of the enhanced powers" but I want clarity on what the current configuration CAN achieve. I don't believe we have that yet. <br class=""><br class="">Chris Disspain<div class="">CEO - auDA</div></div><div class=""><br class="">On 21 Apr 2015, at 17:35, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank" class="">gregshatanipc@gmail.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class="">Chris,<div class=""><br class=""></div><div class="">The simple answer is that the SOACs as currently configured are not a very good vehicle for many of the enhanced powers we seek. Once you make them into members and give them legal personhood everything else becomes much easier. </div><div class=""><br class=""></div><div class="">However, you assumed no change to the SOACs, which made the answers much harder.<span class=""></span></div><div class=""><br class=""></div><div class="">Greg<br class=""><br class="">On Tuesday, April 21, 2015, Chris Disspain <<a href="mailto:ceo@auda.org.au" target="_blank" class="">ceo@auda.org.au</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><span style="font-family: Verdana; font-size: 13px; color: rgb(102, 102, 102);" class="">Greg, All,<div class=""><br class=""></div><div class="">With respect, I think we are overcomplicating the issue. I simply want to gain a base line for the discussion about any changes necessary to achieve what we want. We agreed on jurisdiction that if we can get acceptable escalations and remedies without changing jurisdiction then we should leave well alone for now, I think we should apply the same principle here. I am clear what the lawyers recommend we do BUT I am not clear about what we can do or what compromises we need to make if we were to maintain the current structure. I think that is a key part of our deliberations. </div><div class=""><div class=""><p class=""><br class=""></p><p class=""><br class=""></p><p class="">Cheers,</p><p class=""><br class=""></p><p class="">Chris</p></div></div></span></div></blockquote></div></div></blockquote></div></blockquote></div></blockquote></div></blockquote></div></blockquote></div></blockquote></div></div></span></div></blockquote></div>--<span class="Apple-converted-space"> </span><br class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Jordan Carter<br class=""><br class="">Chief Executive<span class="Apple-converted-space"> </span><br class=""><b class="">InternetNZ</b><br class=""><br class="">04 495 2118 (office) |<span class="Apple-converted-space"> </span><a href="tel:%2B64%2021%20442%20649" value="+6421442649" target="_blank" class="">+64 21 442 649</a><span class="Apple-converted-space"> </span>(mob)<br class=""><a href="mailto:jordan@internetnz.net.nz" target="_blank" class="">jordan@internetnz.net.nz</a><span class="Apple-converted-space"> </span><br class="">Skype: jordancarter<br class=""><br class=""><i class="">A better world through a better Internet </i><br class=""><br class=""></div></div></div></div></div></div></div><span class="">_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank" class="">Accountability-Cross-Community@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br class=""></span></blockquote></div><br class=""></div></span></div><br class="">_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br class=""><br class=""></blockquote></div><br class=""></div></blockquote></div><br class=""></div></div></span><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; float: none; display: inline !important;" class="">Accountability-Cross-Community mailing list</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; float: none; display: inline !important;" class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a></span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; float: none; display: inline !important;" class=""><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span></div></blockquote></div><br class=""></div></div></blockquote></div><br></div><style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #9443fb}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #9443fb; min-height: 16.0px}
</style></span></body></html>