From jmaimon at chl.com  Wed Oct  6 12:44:34 2010
From: jmaimon at chl.com (Joe Maimon)
Date: Wed, 06 Oct 2010 12:44:34 -0400
Subject: [arin-discuss] Jabber for remote participants
Message-ID: <4CACA772.5000105@chl.com>

Anyone else having any trouble joining the chat rooms?

Joe


From scottleibrand at gmail.com  Wed Oct  6 13:17:28 2010
From: scottleibrand at gmail.com (Scott Leibrand)
Date: Wed, 6 Oct 2010 13:17:28 -0400
Subject: [arin-discuss] Jabber for remote participants
In-Reply-To: <4CACA772.5000105@chl.com>
References: <4CACA772.5000105@chl.com>
Message-ID: <016901cb657a$5be10480$13a30d80$@com>

ARIN has to register your nick with the jabber client.  If they haven't
already contacted you, I'd e-mail info at arin.net to have them fix that.

-Scott

-----Original Message-----
From: arin-discuss-bounces at arin.net [mailto:arin-discuss-bounces at arin.net]
On Behalf Of Joe Maimon
Sent: Wednesday, October 06, 2010 12:45 PM
To: arin-discuss at arin.net
Subject: [arin-discuss] Jabber for remote participants

Anyone else having any trouble joining the chat rooms?

Joe
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (ARIN-discuss at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-discuss
Please contact info at arin.net if you experience any issues.



From bmanning at vacation.karoshi.com  Thu Oct  7 19:39:34 2010
From: bmanning at vacation.karoshi.com (bmanning at vacation.karoshi.com)
Date: Thu, 7 Oct 2010 23:39:34 +0000
Subject: [arin-discuss] HOWTO: Disenfranchise Voters
Message-ID: <20101007233934.GA10912@vacation.karoshi.com.>


This may only effect a small percentage of folks now, but one might be careful
in the future as some of these things may contribute to confusion in the days ahead.


Preliminary Conditions:

	) legacy address space, covered by LRSA
	) NRPM on transfers
	) A localized ARIN-convenience to help effect a transfer
	) a recent bylaws change to restrict organizationali(ARIN) capture.

My company undertook to transfer some of its resources to its customers as a part of an
overall restructuring activity.  The transfers were concluded successfully.  In the process,
ARIN found it useful to modify (and then reauthorize) our ORGID.  Apparently when the ORGID
was regenerated, it was created with a BRAND_NEW start date.  My organizations decade-plus
history as an ARIN member was reset based on the last transfer.  Guess what that did?

It triggers a clause in a recent change in the bylaws on whom is allowed to vote in ARIN
elections.  In summary, (to prevent capture) an organization hss to have a proven track
record with ARIN (a year), before being allowed to vote in an election.

Whoops!  There was a typo, which moved the last transfer date from EP.NET from last year
to the current year.  ARIN staff was notified and the date was corrected to the date of 
the last transfer.  So voting was accomplished.  This time.


Something to remember going forward.


--bill