<div dir="ltr">One of the things that came up in the last consultation to expand the board was a specific ask wrt <div>restrictions with the newly added seats, such as ensuring regionality (Canada, US, Caribbean),</div><div>Gender, representative of member types (large IPS, small ISP, content provider, rural)...</div><div><br></div><div>I think this whole discussion would be more fruitful if as you say, we agreed on </div><div>requirements wrt the new board seats (and possibly some or all of the old ones).</div><div>"This idea would probably make more sense if the specific</div><div>diversifications desired were assigned to these new roles."</div><div><br></div><div>I am less concerned about if these new board seats are voting or non-voting, </div><div>so long as the have equal access to the board discussions and presence at the votes.</div><div><br></div><div>In short, what wider representation of the Internet community is needed, and </div><div>what restriction would be applied to the seats to ensure that.</div><div><br></div><div>__Jason</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Apr 8, 2018 at 2:43 PM <<a href="mailto:bzs@theworld.com">bzs@theworld.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I have no particular problem with expanding the board, let a thousand<br>
flowers bloom (or ten anyhow.)<br>
<br>
HOWEVER, my unsolicited idea is why not create either multiple kinds<br>
of board positions, where by "multiple" I'm thinking two at least to<br>
begin, voting/non-voting or similar.<br>
<br>
Or another (small) "advisory" -- pick a word, let's not get hung up on<br>
terminology -- board with enough teeth that it's not just token.<br>
<br>
I'd argue, for starters, just being in the room and having a role and<br>
access to the same information would be enough to make it more than<br>
just token.<br>
<br>
A lot of diversity depends on just being heard effectively as much as<br>
specific voting/veto powers.<br>
<br>
This idea would probably make more sense if the specific<br>
diversifications desired were assigned to these new roles.<br>
<br>
That could even be a transitional change, something to do for some<br>
number of years, review the result, and take up expanding the board<br>
per se, or not, at a later date.<br>
<br>
P.S. I do realize this would be more work in terms of organizational<br>
and by-laws changes, etc than just expanding the existing board. It's<br>
not as simple as changing a number. The new structures would have to<br>
be defined and incorporated into existing structures including no<br>
doubt legal considerations (e.g., how would such a newly defined role<br>
be indemnified?)<br>
<br>
--<br>
-Barry Shein<br>
<br>
Software Tool & Die | bzs@TheWorld.com | <a href="http://www.TheWorld.com" rel="noreferrer" target="_blank">http://www.TheWorld.com</a><br>
Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD<br>
The World: Since 1989 | A Public Information Utility | *oo*<br>
_______________________________________________<br>
ARIN-Consult<br>
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br>
List (<a href="mailto:ARIN-consult@arin.net" target="_blank">ARIN-consult@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br>
Help Desk at <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>