From andrei at ripe.net Tue Oct 10 12:05:09 2000 From: andrei at ripe.net (Andrei Robachevsky) Date: Tue, 10 Oct 2000 12:05:09 +0200 Subject: Some migration issues Message-ID: <39E2E9D5.27CABCEB@ripe.net> Dear colleagues, To facilitate discussion on the list let me bring up some of transition 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. 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). A better way would be if the 'owners' could fix this themselves before the transition. 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 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. 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. Your comments are appreciated. Regards, Andrei ---- Andrei Robachevsky DB Group Manager RIPE NCC From woeber at cc.univie.ac.at Thu Oct 12 15:24:36 2000 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Thu, 12 Oct 2000 15:24:36 MET-DST Subject: Some migration issues Message-ID: <009F17E8.FEBDA710.5@cc.univie.ac.at> >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. From andrei at ripe.net Fri Oct 13 18:05:04 2000 From: andrei at ripe.net (Andrei Robachevsky) Date: Fri, 13 Oct 2000 18:05:04 +0200 Subject: Some migration issues References: <009F17E8.FEBDA710.5@cc.univie.ac.at> Message-ID: <39E732B0.224BA191@ripe.net> "Wilfried Woeber, UniVie/ACOnet" wrote: > > >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? > 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 > > Did yo try to get in touch with those? If yes, what was the result? We are working on this. > > >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? Yes. > > >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. > >Your comments are appreciated. > > > >Regards, > > > >Andrei > > > >---- > >Andrei Robachevsky > >DB Group Manager > >RIPE NCC > > Wilfried. Regards, Andrei From woeber at cc.univie.ac.at Fri Oct 13 18:48:56 2000 From: woeber at cc.univie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Fri, 13 Oct 2000 18:48:56 MET-DST Subject: Some migration issues Message-ID: <009F18CE.B4578240.4@cc.univie.ac.at> 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. From andrei at ripe.net Fri Oct 27 10:26:07 2000 From: andrei at ripe.net (Andrei Robachevsky) Date: Fri, 27 Oct 2000 10:26:07 +0200 Subject: reimp.ripe.net (rpsl.ripe.net) server is temporarily unavailable Message-ID: <39F93C1F.10E85E70@ripe.net> Dear Colleagues, Yesterday a machine that was used for the new prototype DB server crashed and could not be restarted due to hardware problems. We are working on this and will bring the prototype server up as soon as possible. Sorry for any inconvenience. Regards, Andrei Robachevsky DB Group Manager RIPE NCC