current filtering too hostile for new prefixes?

Woohyong Choi whchoi@cosmos.kaist.ac.kr
Sat, 7 Aug 1999 20:41:28 +0900


Greetings!  I'm in charge of the new pTLA APAN-KR (3ffe:8040::/28)
and have been trying to get stable routing during the past week. 

What I realized is that many of the 6bone routers already have
very strict filter rules in place, and route advertizement from
my primary peer 6TAP didn't get through most of you.

Could you please update your filters to permit this prefix
accepted (and even redistributed)?

This led me to also think about "what is a good filtering policy
for 6bone routers?"

This is my current configuration for import filter. (for Zebra
and hopefully for Cisco too?)

neighbor <PEER> prefix-list import in
!
ip prefix-list import seq 5 permit 3ffe::/16 le 28 ge 24
ip prefix-list import seq 10 permit 2010::/16
ip prefix-list import seq 99 deny any

My intension is to be more forgiving for what I receive and
to be more strict in what I'm sending out.  I have to list
up every prefix I send out.

Any comments?

Thanks,
-whchoi