mnt-routes in allocation objects

Dear all,

This is to inform you that the RIPE NCC Registration Services will update all 
inetnum objects representing allocations made by the RIPE NCC to Local IRs 
(status: ALLOCATED PA") adding a mnt-routes attribute. We will use the 
maintainer specified in the mnt-lower attribute of the particular inetnum 
object. We will only add a mnt-routes attribute to allocation objects that 
have exactly one mnt-lower attribute (*). The updates will start on Monday, 
10th December 2001.

Until the introduction of RPSL there was no mnt-routes attribute. Adding a 
mnt-routes attribute to the inetnum object representing your allocation will 
enable you to create route objects matching the exact size of your allocation 
object. (You might have to pass other authorisations.) For a graphical 
overview of "Route Object Creation - Getting Authorisation from IP Space" 
please see: <http://www.ripe.net/ripencc/faq/database/route-creation-IP-space-c
heck.html>.

For more information about route object please read:
<http://www.ripe.net/ripe/docs/databaseref-manual.html#1.2.15> and
<http://www.ripe.net/ripe/docs/databaseref-manual.html#3.6.5>.

(*) In general: If you want to update an object maintained by the 
RIPE-NCC-HM-MNT please send a message to <lir-help at ripe.net> including your 
registry ID and the revised object. Please note that we only accept these 
requests from official LIR contacts who are registered in our RIPE NCC 
internal registry files.

If you have any further questions please do not hesitate to contact 
<lir-help at ripe.net> including your registry ID.

Kind regards,

Sabrina Waschke

--

o------------------------------------------o
| Sabrina Waschke         sabrina at ripe.net |
| Registration Services Operations Manager |
|                                          |
| RIPE NCC             tel +31 20 535 4444 |
| www.ripe.net         fax +31 20 535 4445 |
o------------------------------------------o