Hi,

Dear Colleagues,

[...]

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.

Yes. Agree. Been hinting customers to trash/modify such names prior to migration date - not knowing whether or not such conflict would be treated auto-magically... Regards Michael

Your comments and suggestions are appreciated.

Best regards,

Andrei Robachevsky DB Group Manager RIPE NCC

-- Michael Hallgren, Eng., Teleglobe, MH2198-RIPE