more specific routes in today reality

On Tue, 9 Oct 2001 22:51:31 +0200 (MEST)
Robert Kiessling <Robert.Kiessling at de.easynet.net> wrote:

> Jan-Ahrent-Czmok writes:
>> I am not referring to 192.0.0.0/8, but in this case, we shall include an
>> option to return old swamp space to their respective registry and issue
>> address space from ripe.

> So what are you refering to? Please name examples of your wild claim:

Okay, let's see if i find it:

192.124.115.0/24 == weblease AG, old address space from pre-ARIN, region should be
ARIN/USA, is used in DE 
(okay -- no direct /16 or smaller announcement), but an example of the bad usage in
the swamp space.

inetnum:      194.13.111.0 - 194.13.111.255

route-server>sh ip bgp 194.13.111.0/24 shorter-prefixes 
*  194.13.0.0/17    12.123.25.245                          0 7018 3549 1103 1103 i

> In particular:

> - In which way is XLink special so that by dropping /24 routes, they
> would receive non-customer traffic?

xlink used to keep some of the old swamp space overtook from uni karlsruhe

> - RIPE announces exactly 193.0.0.0/21. So how would traffic magically
> end up at RIPE if you applied strict filters?

i am NOT referring to RIPE announced routes.

>> > so if I filter those, why should the traffic go to XLink?    Why should
>> > *any* traffic go to RIPE?  It will be just blackholed (or default-routed
>> > to one of my upstreams, if I happen to have a default-route).
>> 
>> "if" you have a default route. Default route if multi-homed is surely bad IMHO.

> Nonsense again. Traffic will be blackholed only if you have *no*
> default route.

If you have a default route when multihomed, you create routing loops, when not filtering
at both ends of the "transits". This created nice loops :-((

--jan


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