Thanks John. I saw the "discretion" bit and did not know how lenient
your team was being.
In that case, I think we ought to loosen up the language of this section
then; while 464xlat is a mature technology (with a native CLAT in
Windows as of... this week), I would be downright scared to try to run a
client network that way today.
Eric C. Landgraf
Virginia Tech
On Oct 30 16:30, John Sweeting wrote:
> Hi Eric,
>
> 4.10.
> ARIN shall allocate a contiguous /10 from its last /8 IPv4 allocation from
> IANA. This IPv4 allocation will be set aside and dedicated to facilitate IPv6
> deployment. Allocations and assignments from this block must be justified by
> immediate IPv6 deployment requirements. Examples of such needs include: IPv4
> addresses for key dual stack DNS servers, and NAT-PT or NAT464 translators.
> ARIN staff will use their discretion when evaluating justifications.
>
> Dual stacking is only a justification for key infrastructure, deploying full
> dual stack for customers is not a justification.
>
> Thanks,
> John S.
>
>
> From: ARIN-PPML <[email protected]> on behalf of Eric C. Landgraf
> <[email protected]>
> Date: Friday, October 30, 2026 at 12:18 PM
> To: [email protected] <[email protected]>
> Subject: Re: [arin-ppml] ARIN 58 Table Topic - If the Waitlist didn't exist,
> what would?
>
> On Oct 29 23:21, Mark Van Daele via ARIN-PPML wrote:
> > 4. Don't redirect recovered space to 4.10, it certainly doesn't need it now
> > and won't for a very long time. At ARIN 54, staff reported 13,938 /24s
> > remaining in the 4.10 pool, with less than 400 issued per year. That is more
> > than 34 *years* of supply at the current rate. The same report noted it
> > would take about 1,727 /24s to clear the waitlist, against quarterly
> > distributions averaging around 95 /24s. Recovered space sent to 4.10 would
> > sit idle for literal *decades* while new operators wait. If anything set a
> > smaller 4.10 reservation pool (3 years?) and refill it vi 4.1.7 as blocks
> > arrive. That frees up space to be issued *now* to fill need.
>
> Hi Mark,
>
> Thanks for your insight. To channel my inner John Curran: it's your
> community and we need your feedback. :)
>
> I think reducing the size of the 4.10 pool is a good potential policy
> proposal. You're right that the pool is oversized for what we need, and
> a large distribution from it could be used to either fully wrap up the
> waitlist (if the community decides that's what they want), or to create
> a major policy change in the waitlist without "grandfathering". With how
> rapidly ARIN has been fulfilling the waitlist lately, I think 4.1.7 is
> more than sufficient to keep 4.10 operating even with a smaller pool, or
> no reserved pool at all.
>
> For the organizations you support, why is 4.1.8 space preferable to 4.10
> space? If they are deploying dual-stack, it should be relatively easy to
> justify an allocation of 4.10 space instead of sitting on the waitlist:
> it is my understanding that a dual-stack network is "facilitating IPv6
> Deployment" and therefore *should* be allowed as a 4.10 justification.
> And if ARIN is not implementing it this way, then I think that warrants
> a policy proposal.
>
> Regards,
> Eric C. Landgraf
> Virginia Tech
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.