Hi all, already twice customers of us were not able to update route records, because RIPE had not included mnt-routes (and mnt-lower) lines into the inetnum object when allocating a block. The blocks where we experienced the problem were allocated in 1996: inetnum: 193.203.96.0 - 193.203.127.255 and 1999: inetnum: 212.95.64.0 - 212.95.95.255 This is not an easy to understand problem for small ISPs dealing with route objects only now and then. To solve this problem it is necessary that LIRs send the inetnum object to be updated to hostmaster@ripe.net and RIPE update the object with RIPE-NCC-HM-MNT. Only then the ISP can update their route records. Question: - Is there a reason for not existing mnt-lower and mnt-routes lines? - If not, can RIPE update all affected inetnums in an automatic manner? This would really help a lot, because manual updates create a lot of consultancy need from upstream providers (us in this case) and, I guess, a considerable workload on the RIPE hostmaster team. Regards Karsten ------------------------------------------------------------- Karsten Koepp IP Network Planning Lambdanet Communications GmbH (AS13237) Guenther-Wagner-Allee 13 D-30177 Hannover (Germany) Phone +49 (0)511 / 84 88 - 12 55 Fax +49 (0)511 / 84 88 - 12 59 Mobile +49 (0)178 / 3 62 - 12 55 mailto:Karsten.Koepp@lambdanet.net News & Facts on our Website: www.lambdanet.net -------------------------------------------------------------