<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: Calibri, sans-serif; font-size: 14px;">be of an introductory nature. The proposed agenda is:</span><br><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;"><div><ul><li>Roll Call / Statements of Interest</li></ul></div></div></blockquote><div><br></div>Suggestion: only reading SoI for people that do not have GNSO SOIs (or have updates to), to shorten up this part. </div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;"><div><ul><li>Applicability of ICANN principles of transparency and openness</li><li>Items for initial review - GNSO Resolution forming this group, GNSO Working Group Guidelines, GNSO Policy Development Process (to serve as a reference point for the DG)</li><li>Discussion of Work Plan – Review of Interim Chair's Draft Work Plan and discussion of alternatives and tools for completing work</li><li>Election of DG Leaders – The DG may elect to have co-chairs or vice-chairs. Once selected, the DG Chair(s) will need to be confirmed by the GNSO Council.</li></ul></div></div></blockquote><div><br></div></div>May I suggest that no attempt to see vice-chairs as representation of that constituency in the group ? It's so much simpler to have 2 (either chair/vice-chair, co-chair/co-chair, chair/alternate chair) leaders instead of a complex structure... since *-chairs only have coordination but no definition role, it's of no use to see too much into the roles. <div><br></div><div><br></div><div>Rubens</div><div><br></div><div><br><div><div><br></div></div></div></body></html>