Good morning, In article <Pine.LNX.4.33.0301011341580.22323-100000@dot-god.com>, Joe Baptista <baptista@dot-god.com> writes [...]
I understand the 82.0.0.0/8 block suffers from the same problem. From what I can see RIPE has not yet issued any netblocks from this pool. If RIPE does issues blocks from this pool will RIPE take back the IP if it enconters the same problems or will RIPE follow the ARIN approach of no returns even though ARIN and RIPE are aware of the frustration it is causing.
The RIPE NCC has not yet made any allocations from 82.0.0.0/8. All address space from which the RIPE NCC makes allocations is documented in the "Smallest RIPE NCC Allocation / Assignment Sizes" document. The latest version of this document is always available from the following web page: <http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> The RIPE NCC also makes an announcements to various mailing lists when a new block is received from the IANA. The announcement of 82.0.0.0/8 was made on 27 November 2002 and can be viewed in our mail archives at: <http://www.ripe.net/ripe/mail-archives/routing-wg/2002/msg00195.html> The RIPE NCC can not guarantee whether any particular route will be accepted by any network operator. Best regards, -- leo vegoda RIPE NCC Registration Services