<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello All,<div class=""><br class=""></div><div class="">It’s time once again for our quarterly board conference call. It’s scheduled for 6PM (18:00) Pacific, Monday December 28th. We’ll be using our standard conference line at 1-206-805-8861.</div><div class=""><br class=""></div><div class="">The board members will meet to discuss the current state and vote on any decisions necessary for the org. Members are welcome to dial in and listen, and I make a point of asking for general feedback on things being discussed before the board makes a decision.</div><div class=""><br class=""></div><div class="">If anyone has things they would like to have brought up on the agenda, please reach out to me and I’ll be sure to include them.</div><div class=""><br class=""></div><div class="">We’ve currently got on the list:</div><div class=""><ul class="MailOutline"><li class="">Consider refactoring the <a href="http://hamwan.org" class="">hamwan.org</a> web site to be more reflective of the HamWAN community. Puget Sound has been the founding/flagship network, but we have very successful sisters, and the main landing page should be inclusive of them.</li><li class="">Consider a new mailing list for work on progressing the HamWAN standard. This is currently extremely informal, and is driven mostly on IRC.</li><li class="">Consider transitioning the <a href="mailto:psdr@hamwan.org" class="">psdr@hamwan.org</a> mailing list to something more general like <a href="mailto:hamwan@hamwan.org" class="">hamwan@hamwan.org</a>. As with the first point, HamWAN is a standard, and we have a community of sister networks and there should be a general discussion place not specific to Puget Sound.</li><li class="">We’ve had some technical projects come along that have put IP space back in our minds. We’ve had a suggestion to request a /16 for Puget Sound from ARDC, rather than a more incremental increase in our allocation. This would give us quite a bit of room to grow, and we would seem to have some support from our local coordinator. As Puget Sound is the hub for some of our more ambitious projects like the Open Peering Policy, we may be able to have some weight behind this request, but it is a large chunk, that will require large reasons.</li></ul><div class=""><br class=""></div></div><div class="">Thanks,</div><div class="">Nigel</div><div class="">President</div><div class="">HamWAN</div></body></html>