On Wed, Oct 12, 2011 at 11:59:14AM +0400, Tima Maryin wrote: > > RIPE NCC was awared about this issue and now reallocate blocks to those > who got addrs from 128.0.0.0/16
One more update on this topic: RIPE started debogonisation for 128.0.0.0/16, so it looks like this network will be allocated again in the future: route: 128.0.0.0/21 descr: RIPE-NCC-RIS debogon prefix origin: AS12654 pingable: 128.0.0.1 I hope all networks will implement advice from PSN-2011-10-393 before this happens. -- In theory, there is no difference between theory and practice. But, in practice, there is. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp