Some migration issues

>A. Issues that affect objects:
>
>1. Route objects. Since the "withdrawn" attribute is not supported in
>RPSL, route objects containing this attribute will not be migrated.
>Currently there are 9 such objects.

  I guess this is not a big deal.

>2. Mntner objects. Since "AS-" and "RS-" are reserved prefixes in RPSL,
>mntner objects which name starts with one of the reserved prefixes
>should be renamed. The proposed automatic procedure is to add "MNT-" to
>such names (objects and references).

  Or, as the offendin gpart is the "AS-", and all of those names do
  include "MNT" anyway, why not just drop the "AS-" prefix? Would this
  lead to any collisions?

>A better way would be if the
>'owners' could fix this themselves before the transition.

  Agreed :-)

>There are 9 such objects: 
>
>mntner:AS-SIX-MNT
>mntner:AS-5532MNTB
>mntner:AS-ETEL-MNT
>mntner:AS-NETLINK-MNT
>mntner:AS-THENET-MNT
>mntner:AS-INFORMATIK-MNT
>mntner:AS-MNT
>mntner:AS-NEW1-MNT
>mntner: RS-MNT

  Did yo try to get in touch with those? If yes, what was the result?

>B. Issues that affect NRTM clients
>
>1. NRTM server now listens on a separate (non-whoisd) port. For the
>prototype server it is currently 4444, but first you need to contact
>ripe-dbm to unblock access.

  I guess anyone intersted in mirroring has to do that anyway, true?

>2. Object updates are atomic operations in the new version, that is they
>are not split into two: DEL + ADD. This is not a problem with the new
>implementation of NRTM client, but could crash clients based on v2.x
>Perl software.

  I don't understand what the issue is (probably because I don't speak
  that much Perl :-)

>Your comments are appreciated.
>
>Regards,
>
>Andrei
>
>----
>Andrei Robachevsky
>DB Group Manager
>RIPE NCC

  Wilfried.