[arin-ppml] Rationale for /22
Ken.Mix at clearfly.net
Fri Jul 31 11:45:27 EDT 2009
So if you'd been able to get PI /24s, you'd still be announcing those individual blocks instead of a single, larger block?
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of Michael K. Smith - Adhost
Sent: Friday, July 31, 2009 09:39
To: William Herrin; ARIN PPML
Subject: Re: [arin-ppml] Rationale for /22
> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On
> Behalf Of William Herrin
> Sent: Thursday, July 30, 2009 5:40 PM
> To: ARIN PPML
> Subject: Re: [arin-ppml] Rationale for /22
> On Thu, Jul 30, 2009 at 8:10 PM, Michael K. Smith<mksmith at adhost.com>
> > In the
> > past, I've been in just this type of position, advertising multiple
> > assigned from upstreams until I could justify a /20 from ARIN. If I
> had the
> > opportunity to number out of a /24 instead of waiting until I had a
> /22 I
> > would have jumped at the chance.
> Hi Michael,
> Does that mean you actually used *less* BGP slots after getting your
> ARIN addresses? So in your case, current ARIN policy was actually
> counterproductive to its goal, causing you to announce *more* routes,
That is correct. When we went to ARIN space, this was in 1995 mind you, we went from 6 announced PA blocks to one PI block. But, we had to keep getting PA blocks until we could justify the block from ARIN. This happened again in 2000 with another company when we went from 4 PA blocks to one PI block.
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.
More information about the ARIN-PPML