The status of the migration iissues

Dear Colleagues,

As some of you might have noticed, several problems showed up after the
migration. Let me present an update on their status:

1. PGP signed messages sent to <auto-rpsl at ripe.net> didn't pass
authorization checks

This was fixed on 24th of April. Please note that PGP signed updates
cannot be processed by <auto-dbm at ripe.net>. Until 14th of May,
<auto-dbm at ripe.net> processes updates in RIPE-181 format and
automatically translates them into RPSL, which voids PGP signatures.

2. Conversion problems of updates sent to <auto-dbm at ripe.net>

Problematic objects were:
- Objects with syntax errors
- Indented objects (containing leading whitespace)

In both cases objects were not converted to RPSL and user received an
empty acknowledgement.

This was fixed today, 26th of April.

Please note that <auto-dbm at ripe.net> cannot reproduce all the behaviour
of the v2 database. In particular, empty attribute is treated as a
syntax error and Routing Policy System Security authorization rules
apply.

We strongly recommend you to switch to updates in RPSL format as soon as
possible.

Also note, that <auto-dbm at ripe.net> will process updates in RIPE-181
format until 14th of May. After that, updates in RIPE-181 format should
be sent to the new address, <auto-181 at ripe.net>, and <auto-dbm at ripe.net>
will accept only RPSL syntax.

3. Due to above problems some of the updates were not processed. If you
haven't received an acknowledgement from the database one day after you
sent your update we would kindly ask to re-send it.

We apologize for any inconvenience these problems caused. We are working
on some minor problems and rely on your understanding.

Please visit the "Migration Issues" link on the "Database Status" page
(http://www.ripe.net/ripencc/pub-services/db/issues.html) for the
up-to-date information.

Regards,

Andrei Robachevsky
DB Group Manager
RIPE NCC