[address-policy-wg] PA Assignment questions

Hi,

Nolan, Keith schrieb:
[...]
> The suggestion from RIPE NCC was to apply for smaller Assignments from 
> the PA Space and to take each of them from a separate /24 range, and to 
> create a /24 route object for each separate /24 Space, or to apply for 
> PI Space for each location as PI Space was more in-line with what we are 
> trying to achieve.
> 
>  
> 
> While this will work, I have an issue with RIPE NCC providing a work 
> around, and I believe the policy should allow for a LIR to use the PA 
> Allocation in the best manner to conserve IP Space and to not have 
> “Available” networks in PA Space which can never be assigned and to not 
> waste PI space by not allowing a LIR use the Allocated PA Space for its 
> own Infrastructure.

sorry, i don't really understand where the problem with RIPEs 
suggestions is?
Does it matter if /25 of a /24 is assigned or the whole /24 for 
conservation purposes?!
If you don't need the full /24, it's wasted in any way? Or did i get you 
wrong?

And please, sorry, PA == Provider AGGREGATED. If you don't aggregate, 
you will run into problems like LIR Allocation Size filters in some 
places anyways.
You just set this up the wrong way.

Seems like you designed something without understanding all the 
implications?

Also, PI or PA is only a policy thing, what's the waste in using PI over 
PA? Nothing, a PI /24 is a /24 like a PA /24 is ...

Again, sorry, i don't understand your problem. RIPEs suggestion is 
perfectly valid. Using PI instead of PA will even safe you the hassle 
with connectivity issues you will get announcing /24s out of a PA block 
with minimun allocation size like /21 - you will get filtered by some 
networks.

Get your design right might be the best solution (no offencement!).
What you want to do is actually the workaround, not RIPEs solution.

-- 
========================================================================
= Sascha Lenz                  SLZ-RIPE          slz at baycix.de         =
= Network Design & Operations                                          =
= BayCIX GmbH, Landshut                  * PGP public Key on demand *  =
========================================================================