Some migration issues
Wilfried Woeber, UniVie/ACOnet woeber at cc.univie.ac.at
Fri Oct 13 18:48:56 CEST 2000
Hi Andrei, => >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? => = =No, except for the last three. = => >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 Argh, you are right, AS-MNT -> MNT and RS-MNT -> MNT. Rats. I didn't look close enough. => >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 :-) = =Currently if one submits modification to an object it will produce 2 =operations (serials): deletion of an old version (DEL) and creation of a =new one (ADD). In the new software this will be treated as one operation =with only one serial (ADD) produced. OK, but then what would be the point of trying to run an old client (RIPE-181 style) against the new server (RPSL style)? Hmmmm, there might indeed be "older" PERL-based - but RPSL-aware - packages around that _do_ understand RPSL. I'm the wrong one to comment on that, I think. So, please un-read this paragraph :-) Wilfried.