Summary of the Migration issues

Dear Colleagues,

[Apologies for duplicate messages]

Please let me answer some of your questions.

Frank Bohnsack asked:
 
>> 1.3 In case origin of a route object being created is from non RIPE
>> space, users will need to create corresponding aut-num object in the
>> RIPE DB.
>
> * Means that, all non RIPE IP/ASN space is available on 23 of April as default
>   or should we send an request if needed ?
>

Non RIPE IP space will be protected by the encompassing inetnum object.
There is no need to create a corresponding inetnum object in case of
"foreign" route creation. In case 1.3 people will be able to create a
corresponding aut-num object themselves. 

> * Should we still use the human mail interface for "aut-num" and "mntner"
>   creations on 23 of April ?
>

Yes. Except for aut-num creations in non RIP ASN space (case 1.3), when
the request should be sent to <auto-dbm at ripe.net> or
<auto-rpsl at ripe.net>. 
 
> * Can we assume that the database on 23 of April is the same like the current
>   RPSL mirror ?
>

RPSL mirror is being kept in sync with the production RIPE Database.
That means the contents of the both databases is the same. 

This will slightly change at the beginning of April when we plan to
begin final pre production phase. Several objects (like as-block,
encompassing inetnum) will be added to RPSL database. 

In a few days we are going to present a detailed migration plan, and
your comments are highly appreciated.



Ernesto Baschny asked:

> > PGP authorization scheme will not work with <auto-dbm at ripe.net> robot
> > after 23 April. Updates requiring PGP auth should be sent directly to
> > <auto-rpsl at ripe.net>.
> 
> Does that refer only to route/inetnum objects, or to all (also
> person-objects)?  If so, can person-objects already be created
> using the adress auto-rpsl at ripe.net the same way we used the
> auto-dbm at ripe.net (with PGP)?

This restriction applies to all updates/objects sent in RIPE-181 format
to <auto-dbm at ripe.net>. So if you are using PGP authorization, starting
from 23 of April you should send your updates to <auto-rpsl at ripe.net> in
RPSL format.

To avoid confusion <auto-rpsl at ripe.net> will not be valid until April
23.


Best regards,

Andrei Robachevsky
DB Group Manager
RIPE NCC