Re: [ARIN-consult] Reminder - Consultation on ARIN’s Membership Structure

Owen DeLong owen at
Sun Nov 7 01:07:04 EDT 2021

> On Nov 6, 2021, at 6:57 PM, John Curran <jcurran at> wrote:
>> On 6 Nov 2021, at 6:46 PM, Owen DeLong via ARIN-consult <arin-consult at <mailto:arin-consult at>> wrote:
>> From: Owen DeLong <owen at <mailto:owen at>>
>> Subject: Re: [ARIN-consult] Reminder - Consultation on ARIN’s Membership Structure
>> Date: 6 November 2021 at 6:46:09 PM EDT
>> To: Paul Andersen - ARIN <paul at <mailto:paul at>>
>> Cc: Scott Leibrand <scottleibrand at <mailto:scottleibrand at>>, "<arin-consult at <mailto:arin-consult at>>" <arin-consult at <mailto:arin-consult at>>
>> ...
>> Given ARIN’s historically limited ability to reliably contact end user organizations in a verifiable manner, I think that’s a valid concern.
>> Owen
> Owen - 
> The general case of notification of end-user organizations via obsolete contact information is a valid concern, but is in this particular case the end-user organizations will have just provided updated information (for use as their voting point of contact), so I don’t believe that reliable notification would prove to be an issue.

Color me confused… If they’ve provided a voting contact, then they’ve responded and effectively expressed a designation of someone that they want to vote on their behalf, therefore indicating a desire to vote.

I’m talking about the case for organizations that get a renewal invoice for the new inflated fee and pay it without taking any other action, indicating that it’s not at all unlikely that
the AP department received a pre-approved bill, tossed all the additional matter from the envelope (likely including the envelope) into the round file and paid the bill, never having brought the changes to the attention of anyone who might care about anything beyond paying the bill.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ARIN-consult mailing list