[arin-ppml] Revised - ARIN-2024-10: Registration Requirements and Timing of Requirements With Retirement of Section 4.2.3.7.2
Martin Hannigan
hannigan at gmail.com
Tue Jul 22 15:10:21 EDT 2025
On Tue, Jul 22, 2025 at 2:59 PM William Herrin <bill at herrin.us> wrote:
>
> On Sun, Jul 20, 2025 at 5:11 PM David Farmer via ARIN-PPML
> <arin-ppml at arin.net> wrote:
> > While I’m willing to be convinced otherwise, I see no compelling
> > reason to change from 7 to 14 days. I’m not strongly opposed to
> > 14 days. But if no one is willing to make a first-person argument
> > supporting the change to 14 days, then why make the change?
>
[ clip ]
> Devil's advocate: 7 days means the IP address manager who isn't
> updating ARIN records with automation can't take a normal vacation. 14
> days is enough for someone to get their sunburn and then return and
> process the backlog.
We can't write policy based on recipient benefit or PTO programs. Many
companies offer more than a week and authorize two. It doesn't scale.
While we were told some large companies can't get it done, no-one said
why. Without that add-on, I'd assume opex and then compare to the
smaller networks who (so far) have not complained. A little equity?
If it were because ARIN's systems are too slow for the volume, that
could be interesting.
HTH,
-M<
More information about the ARIN-PPML
mailing list