Missing mnt-routes in ALLOCATED PA objects

Dear Karsten,

Please see Sabrina Waschke's message regarding the issue: 

http://www.ripe.net/ripe/mail-archives/db-wg/20010701-20020101/msg00099.html

If you have any more questions, please don't hesitate
to contact <ripe-dbm at ripe.net>.

Regards,

Engin Gunduz
____________________________
RIPE Database Administration.


Karsten Koepp wrote:
>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 at 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