On Mon, 6 Dec 1999, Lars Marowsky-Bree wrote:
Which is a (serious?) waste of address space, since it requires at least two times the same assignment. On the other hand, it saves one ASN and one potential new buggy AS is kept away from the BGP4, so it probably evens out.
Agree with that part, though everything depends on NAT implementation (the possibility of address reusage) and the size of the customer network. And yes - it doesn't provide all the benefits that BGP does. On the other hand, convincing RIPE NCC to provide PI addresses might even be much easier than convincing Sprint to remove their filters for such customer networks. The main reason Sprint uses to filter BGP announcments on /19 is the size of the routing table and a large amount of updates for small networks. Regards, Beri -- ----- ___ Berislav Todorovic, Network Engineer ---- / / /____ ____ _/_ -- KPNQwest N.V. - IP NOC (formerly EUnet) --- /--- / // //___/ / --- Singel 540, 1017 AZ Amsterdam, NL -- /___ /___// //___ /_ ---- Phone: (+3120) 530-5333; Fax: (+3120) 622-4657 - --- Email: beri@EU.net