<div dir="ltr">Thank you for this impassioned defense, Mark. Indeed, with the idea that anyone can join the mailing list, listen in on the conversations, and choose to be as active or inactive as they want, any individual not only has the right to do so but increases the accountability and transparency of our processes.<div><br></div><div>What I am thinking instead since this point has been raised is connected to the annual check-in process. Since we already check to see if people who have signed up have an active email address (for the purposes of voting), I think we should maintain a policy that as long as someone has signed up, has an active address, and is not engaging in blatantly obstructing behavior (e.g., spamming the list(s)), such members have every right to recieve updates and mails, as Mark so brilliantly highlighted.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Moreover, discerning the criteria to essentially remove someone from NCSG/NCUC is a pandora's box in and of itself. </div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,<br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><font size="2" face="arial, helvetica, sans-serif">-Michael<br></font></div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><br></div></div></div>
</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Sep 9, 2016 at 9:13 AM, Mark Leiser <span dir="ltr"><<a href="mailto:markleiser@gmail.com" target="_blank">markleiser@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would vigorously object at the suggestion that "passive members" get kicked out the constituency and would suggest not only is it completely off course, but also offensive and counterproductive. I am one of the "passive members" you refer to and hardly ever post on these threads, yet I read every email and contemplate the implications of the discussions and debates that come into my Inbox. I may be a "passive member" here, which is what you seem to want to judge me on, but am active in promoting civil society's role in Internet Governance in my academic setting (I teach Internet Governance on our LLM Programme at my home institute and discuss NCSG's role within ICANN to a lesser extent when teaching at the London School of Economics. <div><br></div><div>My "passivity" turns "active" when I take what I have learned and through silent contemplation, write extensively about the role of civil society in Internet Governance and particularly the NCSG's role in fighting back against IP owners and other non-state actors over governance. </div><div><br></div><div>Enter shameless plug for my chapter in the forthcoming Oxford Handbook on the Law and Regulation of Technology. Oxford University Press: <a href="http://strathprints.strath.ac.uk/54396/" target="_blank">http://strathprints.<wbr>strath.ac.uk/54396/</a></div><div><br></div><div>I feel incredibly passionate about the role of NCUC and NCSG in holding ICANN to check. I didn't think I'd have to post here from time to time in order to validate my feelings...</div><div><br></div><div>Mark </div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div style="font-size:small"><p><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#500050">Mark </span></p><p><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#500050"><br></span></p><p><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#500050">Mark Leiser, BSc, LLB (Hon) |
Teaching Associate and PhD Candidate | University of Strathclyde | Faculty of
Humanities and Social Science | The Law School l Centre for Internet Law and
Policy | LH306 | Lord Hope Building | 141 St James Road | Glasgow G4
0LT | Tel. <a href="tel:%2B44%20141-548-2493" value="+441415482493" target="_blank">+44 141-548-2493</a></span><span style="font-size:10.0pt"></span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#500050"> </span></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11pt;font-family:Arial,sans-serif"><a href="mailto:markleiser@gmail.com" target="_blank">Email</a> </span><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#500050">|</span><span style="font-size:9pt;font-family:Arial,sans-serif"> <a href="https://www.strath.ac.uk/humanities/courses/gradschool/studentprofiles/markleiser/" target="_blank">Bio</a> </span><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#500050">| </span><span style="font-size:9pt;font-family:Arial,sans-serif"><a href="http://twitter.com/#!/mleiser" target="_blank">Twitter</a> </span><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#500050">| </span><span style="font-size:9pt;font-family:Arial,sans-serif"><a href="http://www.linkedin.com/profile/view?id=189149411&trk=tab_pro" target="_blank">Linked<wbr>In</a> </span><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif;color:#500050">|</span><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif"> </span><span style="font-size:9pt;font-family:Arial,sans-serif"><a href="https://plus.google.com/u/0/105289982691060086995/posts" target="_blank">Google+</a> </span><span style="font-size:11.0pt;font-family:"Tahoma",sans-serif"></span></p></div></div><div><br></div></div></div></div></div></div></div></div></div></div><div><div class="h5">
<br><div class="gmail_quote">On 9 September 2016 at 06:45, Raoul Plommer <span dir="ltr"><<a href="mailto:plommer@gmail.com" target="_blank">plommer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>This might be completely off course, but should we have a way to kick out passive members, who haven't done anything for ... one or two years? That ten percent could become unattainable eventually.<br><br></div>-Raoul<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On 9 September 2016 at 02:59, Rafik Dammak <span dir="ltr"><<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_extra" style="font-size:12.8px">Hi everyone,</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">I am glad to share with you this important announcement, on behalf of NCUC EC, to start the NCUC Bylaws change process.</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">There were previously several attempts to amend the bylaws/charter to update it and align it with NCSG charter. For this time and as the bylaws allowed it, the NCUC EC decided to work as drafting team and propose an amended draft version for consultation based on previous drafting teams and volunteers work. I want to thank everyone who participated on those precedent efforts. </div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">In term of timeline, we are going to follow this basically:</div><div class="gmail_extra"><div class="gmail_extra" style="font-size:12.8px;color:rgb(80,0,80)"><br></div><div class="gmail_extra"><div class="gmail_extra"><ul style="font-size:12.8px"><li style="margin-left:15px"><span style="font-size:12.8px"><font color="#500050"> <b> </b></font><font color="#000000"><b>Call for input</b>, <b>first reading</b> from <u>9th September till 8th Octobe</u>r </font></span></li></ul><div><a href="https://docs.google.com/document/d/1wYP4-JGKA_u6QligvViBkygzj8Q62kmFF-ky5XSWWDU/edit#heading=h.30j0zll" style="font-size:14.6667px;font-family:calibri,sans-serif" target="_blank">NCUC Charter Amendments</a><span style="font-size:14.6667px;color:rgb(31,73,125);font-family:calibri,sans-serif"> </span>First Draft<font style="font-size:12.8px" color="#000000"><br></font></div><div style="font-size:12.8px"><span style="color:rgb(31,73,125);font-family:calibri,sans-serif;font-size:14.6667px"><br></span></div><span style="font-size:12.8px">NB During this time, the EC will regularly monitor the doc for questions and comments and attempts to resolve them. Teleconferences can be held as well to resolve issues and update members on our progress</span><br><ul style="font-size:12.8px"><li style="margin-left:15px"><font color="#000000"><span style="font-size:12.8px"> <b><u>First resolution of comments</u></b> 8th October to 9th October by NCUC EC</span><br></font></li><li style="margin-left:15px"><font color="#000000"><span style="font-size:12.8px"> <b>Call for input, second reading</b> for amended draft, <u>9th October to 9th November</u></span><br></font></li><li style="margin-left:15px"><font color="#000000"><span style="font-size:12.8px"> <b>Consultation about the charter during NCUC ad-hoc meeting</b> in Hyderabad (tentative date is 6th November)</span><br></font></li><span><li style="margin-left:15px"><font color="#000000"><span style="font-size:12.8px"> <b>Final call</b> : <u>9th November to 12th November</u> , to take note of any objections</span><br></font></li></span><li style="margin-left:15px"><font color="#000000"><span style="font-size:12.8px"> <b>Final draft ready</b> by <u>13th November</u> to be approved by NCUC EC</span><br></font></li><li style="margin-left:15px"><font color="#000000"><span style="font-size:12.8px"> <b> Voting </b>in parallel with NCUC election (tentative dates </span><span style="font-size:12.8px"><u>14 Nov. - 27 Nov</u></span><span style="font-size:12.8px">) to adopt the new charter.</span><br></font></li><li style="margin-left:15px"><span style="font-size:12.8px"><font color="#000000"> <b>When adopted</b>, informing the ICANN staff about the new charter, process with ICANN board/staff/OEC (Organizational Effectiveness Committee) starts. That process is outlined and explained at the bottom</font></span><br></li></ul></div><div class="gmail_extra" style="font-size:12.8px"><font color="#000000">As working method, we are going to follow this:</font></div><div class="gmail_extra" style="font-size:12.8px;color:rgb(80,0,80)"><br></div><div class="gmail_extra" style="font-size:12.8px"><div class="gmail_extra"><ul><li style="margin-left:15px"><span style="color:rgb(0,0,0);font-size:12.8px">The clean version of draft is shared in google doc </span><a href="https://docs.google.com/document/d/1wYP4-JGKA_u6QligvViBkygzj8Q62kmFF-ky5XSWWDU/edit?usp=sharing" style="font-size:12.8px" target="_blank">here</a><span style="color:rgb(0,0,0);font-size:12.8px"> and you can find the attached redline version to see the changes. </span><span style="color:rgb(0,0,0);font-size:12.8px">For those who cannot access we can provide a doc version and will input their comments on their behalf. The google doc is in comments mode (and keeping trace of the discussion, please identify yourself when you comment) and your input is highly encouraged to be made there but discussion can happen in NCUC list.</span></li><li style="margin-left:15px"><font style="font-size:12.8px" color="#000000">F</font><span style="font-size:12.8px;color:rgb(0,0,0)">arzaneh as EC member will be the editor/penholder. The EC will respond to the comments and try solve any issue or questions.</span></li><li style="margin-left:15px"><span style="color:rgb(0,0,0);font-size:12.8px">During each readings, we will try to resolve comments, explain rationale behind amendments. We will keep a clean version as output from a reading .</span></li><li style="margin-left:15px"><span style="color:rgb(0,0,0);font-size:12.8px">We will organize conference calls during each reading/consultation to respond to questions and resolve pending issues, in addition to a dedicated session in Hyderabad ICANN meeting (where remote participation channels will be provided too)</span></li><li style="margin-left:15px"><span style="color:rgb(0,0,0);font-size:12.8px">We will organize a first a Q&A call about the process and to clarify about ICANN process side. We will create a page in our website to document the process and keep the documents there for tracking.</span></li><li style="margin-left:15px"><span style="color:rgb(0,0,0);font-size:12.8px">The NCUC EC will respond to questions/inquiries in the mailing list.</span></li></ul></div></div></div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px"><b>Adoption process</b></div><div class="gmail_extra" style="font-size:12.8px"><b><br></b></div><div class="gmail_extra" style="font-size:12.8px">according to section VIII of the current bylaws, to amend the bylaws we need:</div><div class="gmail_extra" style="font-size:12.8px"><p style="border:0px;font-stretch:inherit;line-height:21px;margin:1.6em 0px;padding:0px;vertical-align:baseline;word-wrap:break-word"><i><font color="#000000" face="arial, helvetica, sans-serif">A. Changes to this charter may take place by vote of the Members. Changes may be proposed by the Executive Committee or by petition of the Members. A petition of ten (10) percent of the then-current members shall be sufficient for putting a charter amendment on the ballot for consideration at the next regular election. Alternatively, the Executive Committee by majority vote may propose an amendment for consideration at the next regular election.</font></i></p><p style="border:0px;font-stretch:inherit;line-height:21px;margin:1.6em 0px;padding:0px;vertical-align:baseline;word-wrap:break-word"><i><font color="#000000" face="arial, helvetica, sans-serif">B. Charter amendments shall be passed if at least two thirds of the votes cast in the election favor its adoption (provided 40% or more of the eligible Voters cast a ballot in the election).</font></i></p><p style="border:0px;font-stretch:inherit;line-height:21px;font-family:arial,helvetica,sans-serif;margin:1.6em 0px;padding:0px;vertical-align:baseline;word-wrap:break-word"><font color="#000000">the voting/election period will take this on consideration (under discussion currently) with regard to the ballot and procedures to be defined by the NCUC EC.</font></p></div><font style="font-size:12.8px" face="arial, helvetica, sans-serif"><b>Board/OEC process:</b></font></div><span style="font-size:12.8px"><div class="gmail_extra"><font face="arial, helvetica, sans-serif"><br></font></div><p class="MsoNormal" style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif">At a high level, the GNSO Charter Amendment Process involves a total of four basic phases <u></u></font></p><p class="MsoNormal" style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"> </font></p><p style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif">· Amendment preparations and approval by the charter-amending community;<u></u><u></u></font></p><p style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif">· Staff review and analysis of amendments for potential ICANN organization impacts;<u></u><u></u></font></p><p style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif">· Review of amendments and opportunity for comment by the multistakeholder community; and<u></u><u></u></font></p><p style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif">· Full Board review and action<u></u><u></u></font></p><p class="MsoNormal" style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"> </font></p></span><p class="MsoNormal" style="font-size:12.8px;color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif">According to ICANN staff, the entire Board review process (which involves the last three phases of the process) seems to now be taking about 6 or 7 months (calculating from the formal submission of the amendments to staff). The specifics of the process look like this:<u></u><u></u></font></p><span style="font-size:12.8px"><p class="MsoNormal" style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"> </font></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt"><b><i><u><font face="arial, helvetica, sans-serif">SUMMARY OF GNSO CHARTER AMENDMENT PROCESS (Excerpts)<u></u><u></u></font></u></i></b></p><p style="color:rgb(0,0,0);margin-top:12pt;margin-bottom:12pt;margin-left:0.5in"><i><font face="arial, helvetica, sans-serif">On 28 September 2013, the ICANN Board established a process for the amendment of GNSO Stakeholder Group and Constituency Charters. That process is as follows:<u></u><u></u></font></i></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt"><font face="arial, helvetica, sans-serif"><strong><i>Phase I: Amendment Preparation</i></strong><i><u></u><u></u></i></font></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt"><font face="arial, helvetica, sans-serif"><i>GNSO Stakeholder Groups (SGs) and Constituencies should formulate charter amendments through their own internal processes and notify ICANN Staff as early as practicable (at </i><i><a href="mailto:policy-staff@icann.org" target="_blank"><span style="color:black">policy-staff@icann.org</span></a>) upon initiation and completion (approval) of such efforts.</i></font></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt"><font face="arial, helvetica, sans-serif"><strong><i>Phase II: Staff Review</i></strong><i><u></u><u></u></i></font></p><p style="color:rgb(0,0,0);margin-bottom:12pt;margin-left:0.5in"><i><font face="arial, helvetica, sans-serif">Upon formal receipt of the proposed amendment(s) approved by the community group, ICANN staff will analyze the proposal and, within 10 business days, submit the community proposal with a report to the appropriate Board committee identifying any fiscal or liability concerns.<strong><span style="font-weight:normal"><u></u><u></u></span></strong></font></i></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt"><font face="arial, helvetica, sans-serif"><strong><i>Phase III: Public Comments</i></strong><i><u></u><u></u></i></font></p><p style="color:rgb(0,0,0);margin-bottom:12pt;margin-left:0.5in"><i><font face="arial, helvetica, sans-serif">After Board committee review of the Staff report and the proposed charter amendments, the Board committee will direct the opening of a Public Comment Forum. Upon completion of the Forum, within 30 calendar days, staff will provide a report to the Board committee summarizing the community feedback.<strong><span style="font-weight:normal"><u></u><u></u></span></strong></font></i></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt"><font face="arial, helvetica, sans-serif"><strong><i>Phase IV: Board Review</i></strong><i><u></u><u></u></i></font></p><p style="color:rgb(0,0,0);margin-bottom:12pt;margin-left:0.5in"><i><font face="arial, helvetica, sans-serif">At the next available opportunity after the delivery and publication of the staff report, the appropriate Board committee shall review the proposed charter amendments, the staff report and any community feedback and make a recommendation to the Board.<u></u><u></u></font></i></p><p style="color:rgb(0,0,0);margin-left:0.5in;margin-bottom:0.0001pt;line-height:12pt"><i><font face="arial, helvetica, sans-serif">After receiving a recommendation from the committee, the Board shall either:<u></u><u></u></font></i></p><p class="MsoNormal" style="margin-bottom:6pt;margin-left:1.25in;color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"><i>a.<span style="font-style:normal"> </span></i><i>Recognize the proposed charter amendment by a simple majority vote; or<u></u><u></u></i></font></p><p class="MsoNormal" style="margin-bottom:6pt;margin-left:1.25in;color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"><i>b.<span style="font-style:normal"> </span></i><i>Reject the proposed amendment by a supermajority (2/3) vote and provide a specific rationale for its concerns.<u></u><u></u></i></font></p><p class="MsoNormal" style="margin-bottom:6pt;margin-left:1.25in;color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"><i>c.<span style="font-style:normal"> </span></i><i>If neither above condition is met, the Board will ask for further explanation of the proposed amendments by the community.<u></u><u></u></i></font></p><p class="MsoNormal" style="margin-left:0.5in;color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"><i>In its review of the proposed amendments, the ICANN Board may ask questions and otherwise consult with the affected SG or Constituency. If it is not feasible for the Board to take action on the proposed amendments after two meetings, the Board shall report to the affected SG or Constituency the circumstance(s) that prevented it from making a final action and its best estimate of the time required to reach an action. That report is deemed an "action" under this process. If it is not feasible for the Board to take action on the proposed amendments after four meetings (or after a total of six scheduled meetings), the proposed community amendments will be deemed effective.</i><i><u></u><u></u></i></font></p><p class="MsoNormal" style="color:rgb(0,0,0)"><font face="arial, helvetica, sans-serif"> </font></p><div class="gmail_extra"><font face="arial, helvetica, sans-serif"><span style="color:rgb(0,0,0)">The full process is posted on the</span><span style="color:rgb(0,0,0)"> ICANN GNSO</span><span style="color:rgb(0,0,0)"> </span><span style="color:rgb(0,0,0)">web site at the bottom of this page –</span><a href="http://gnso.icann.org/en/about/stakeholders-constituencies" target="_blank">http://gnso.icann.org/en/abou<wbr>t/stakeholders-constituencies</a><span style="color:rgb(0,0,0)">.<wbr> A pdf version of the process can be viewed and downloaded from this link -</span><span style="color:rgb(0,0,0)"> </span><a href="http://gnso.icann.org/en/about/stakeholders-constituencies/charter-amendment-process-28sep13-en.pdf" target="_blank">http://gnso.icann.org/en/abo<wbr>ut/stakeholders-constituencies<wbr>/charter-amendment-process-28s<wbr>ep13-en.pdf</a></font></div><div class="gmail_extra"><br></div></span><div class="gmail_extra" style="font-size:12.8px">Please feel free to ask any question or clarification about the process and the bylaw draft. We need everyone participation in this process.</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">Best Regards,</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">Rafik Dammak</div><div class="gmail_extra" style="font-size:12.8px"><br></div><div class="gmail_extra" style="font-size:12.8px">NCUC chair</div>
</div>
<br></div></div>______________________________<wbr>_________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org" target="_blank">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" rel="noreferrer" target="_blank">http://lists.ncuc.org/cgi-bin/<wbr>mailman/listinfo/ncuc-discuss</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org" target="_blank">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" rel="noreferrer" target="_blank">http://lists.ncuc.org/cgi-bin/<wbr>mailman/listinfo/ncuc-discuss</a><br>
<br></blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
Ncuc-discuss mailing list<br>
<a href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" rel="noreferrer" target="_blank">http://lists.ncuc.org/cgi-bin/<wbr>mailman/listinfo/ncuc-discuss</a><br>
<br></blockquote></div><br></div></div>