Another issue related to the migration

[Andrei Robachevsky <]

Dear Colleagues,

[Apologies for duplicate messages]

One issue related to RIPE-181 to RPSL migration escaped our attention and has
not been discussed. It is related to reserved prefixes that cannot appear in
object names according to RPSL specification (RFC2622) which says: 
      
"Names starting with certain prefixes are reserved for certain object types. 
Names starting with "as-" are reserved for as set names. Names starting with
"rs-" are reserved for route set names.  Names starting with "rtrs-" are
reserved for router set names. Names starting with "fltr-" are reserved for
filter set names. Names starting with "prng-" are reserved for peering set
names."

Unfortunately "as-name:" attribute is an object name in RPSL and we have 133
aut-num objects with as-name starting with reserved 'AS-' prefix.

Our suggestion how to deal with these objects is:

1. Send a message to the maintainers of these objects asking them to change the
name to avoid conflict with RPSL specification.
2. Give two-week notice period after which ripe-dbm will convert non compliant
as-names using the following mapping: AS-ASNAME -> AS_ASNAME.

This is more a "cosmetic" change as as-name is not even a lookup key in the RIPE
Database.

Your comments and suggestions are appreciated.

Best regards,


Andrei Robachevsky
DB Group Manager
RIPE NCC