more specific routes in today reality

>> 
>> Great! Now we have to collect routing policies from thousands of small LIRs
>> while still have to deal with thousands of small prefixes.

> So?  There is no difference between thousands of PI prefixes and 
> "thousands of small LIRs", except that the latter actually have to
> *pay* for what they cause.

Right. Strong ACK on this.

>> And if the major ISPs stop listening to the more specfic routes then even
>> using the address from PI space won't work (unless you are big enough).

> Yes.  This is what it's all about.  Small PI space really hurts people.

Yep. And therefore these "small" PI stuff should be cleaned up. The User itself
can use it internally and could get a /24 routed from PA space. 

But it is really not the optimum solution, as it waste's ip address space. And
we have enough RFC1918 space...

> Letting "the whole world" see a /16 (from the upstream) and the direct
> peers a /24 (or whatever) means global routing will just work fine (over
> the upstream's PA block) and and IX routing will also work just fine
> (using the more specific).

right, but is it generally used ? 
I see a lot of /24 out of the same block from a /16 announced space globally
(AS5511 for example)


--jan


-- 
 Jan-Ahrent Czmok        		http://www.lambda-solutions.de
 Technical Advisor ISP	    	        Hofdcker Str. 14, 65207 Wiesbaden
 Tel. +49-(0)-174-3074404