[arin-discuss] ARIN Consultation: Changing the Voter Eligibility for ARIN Member Organizations

[Owen DeLong]

On Feb 8, 2013, at 13:20 , ARIN <info at arin.net> wrote:

> Thanks to everyone who participated thus far in the voter eligibility consultation. Before we close the consultation on Tuesday, we wanted to review the discussion to date. We appreciate your valuable feedback.
> 
>  
> 
> The proposed change to voter eligibility was mainly aimed to increase eligibility, and thus number of votes cast, by allowing those Members without a valid Designated Member Representative (DMR) on file to have someone vote. While ARIN does typically have good voter turnout (as compared to other associations), the change was proposed to remove the task of managing the DMR contact that may have been an impediment to some organizations voting.
> 
>  
> 
> There were a number of responses put forth during the consultation:
> 
>  
> 
> Some of you warned ARIN of unintended consequences of such a procedural change including security issues, increased costs, and that "many persons [with] one vote only creates more problems”.
> 

I would summarize that as "many persons [sharing] one vote..."

>  
> 
> There were also ideas presented for an alternate approach including allowing the Admin POC to easily designate which POC should be allowed to cast their organizations one vote.  This approach could potentially eliminate the need for organizations to have a separate POC to maintain (DMR) and more easily allow organizations to vote that don’t meet the existing DMR email criteria:
> 
>  
> 
> Not be that of a role account (info@, hostmaster@, support@)
> Must contain a person's name or initials (joesmith@, joes @, js@)
> Have a domain matching the Organization or DBA name that ARIN has on file

This last one is consistently problematic, esp. for consultants who often don't have an email address affiliated with
the ORG in question and even more often would prefer to maintain a single login for all of their DMR activities
with a single associated email address.

I know it is relatively common for ARIN to end up putting special waivers in place to address this particular issue,
so I would suggest having a documented non-exceptional mechanism for addressing that reality is well worth the
effort.

Owen


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-discuss/attachments/20130208/cb18f5ce/attachment.html>