On 28 Jul 2016, at 04:19, Randy Bush <randy@psg.com> wrote:
-How do you propose to handle any objects that have a version in both databases that are different?
I think this is a question for AfriNIC to consider, not for the RIPE NCC staff.
you dump crap on them and tell them to clean it up. nice.
I can see how it can look that way, but that was not our intent. In short our intent was to 1) not risk interrupting routing, 2) give the real resource holder the ability to clean up (i.e. in the Afrinic IRR). If the Afrinic resource holder does have access to their object in the RIPE DB today, then they can delete the object before this migration. But, unfortunately, in case they don't we (RIPE NCC) do not have a reliable way to determine claims. We believe that it's best that in these cases objects *are* copied over to the Afrinic IRR in phase 3 - so that the actual resource holders can choose to keep, or force delete these objects as needed. The simplest way to do this is by copying all objects. I can see possible smarter scenarios where duplicates are excluded on import, or where Afrinic resource holders can somehow mark their resources as already migrated. But to echo Job, I think this is for Afrinic and their community to consider. Tim
randy