
Hello Andreas, I am reading this by accident. Seems, you have already done your job. You should be able to simply delete the old maintainer yourself, as there is no object refering to the old mnt: 11/11/04 10:47:06 whois -imb sczn-db-mnt@whois.ripe.net whois -h whois.ripe.net -imb sczn-db-mnt ... % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE I guess, you will have to do this in two steps, first change the mnt of the old object, then delete it. regards Karsten
-----Original Message----- From: andreas_s [mailto:lir@sczn.de] Sent: Wednesday, November 10, 2004 6:49 PM To: db-help@ripe.net Subject: help on maintainer object
dear colleagues, on this time, in the ripe-db are the following maintainer objects present:
old -->
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
new -->
mntner: SCZN-MNT descr: Maintainer for all SCZN objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: SCZN-MNT referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
... sorry that i have created two mnt objects. i had intended that i can update the old mnt object.
can you change please all objects with "sczn-db-mnt" links to SCZN-MNT.
after this, can you delete please the old mnt object sczn-db-mnt from the ripe-db.
many thanks and sorry for my mistake.
kind regards,
andreas schneider de.sczn lir staff
+49 431 7171 5152

Koepp, Karsten wrote:
Hello Andreas,
I am reading this by accident. Seems, you have already done your job. You should be able to simply delete the old maintainer yourself, as there is no object refering to the old mnt:
It is still referenced: $ whois -r -i mb,ml,md,mr,mu sczn-db-mnt % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html inetnum: 217.150.144.0 - 217.150.159.255 netname: DE-SCZN-20040616 descr: t-systems cds gmbh descr: PROVIDER Local Registry country: DE org: ORG-tcg2-RIPE admin-c: as3037-ripe tech-c: as3037-ripe status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-lower: sczn-db-mnt mnt-routes: sczn-db-mnt notify: lir@sczn.de changed: hostmaster@ripe.net 20040616 source: RIPE mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE As this is an allocation object you will need to contact hostmaster@ripe.net and ask them to change the mnt-lower: and mnt-routes: to your new maintainer and then you will be able to delete your old maintainer. Regards Denis Walker RIPE NCC
11/11/04 10:47:06 whois -imb sczn-db-mnt@whois.ripe.net
whois -h whois.ripe.net -imb sczn-db-mnt ... % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
I guess, you will have to do this in two steps, first change the mnt of the old object, then delete it.
regards Karsten
-----Original Message----- From: andreas_s [mailto:lir@sczn.de] Sent: Wednesday, November 10, 2004 6:49 PM To: db-help@ripe.net Subject: help on maintainer object
dear colleagues, on this time, in the ripe-db are the following maintainer objects present:
old -->
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
new -->
mntner: SCZN-MNT descr: Maintainer for all SCZN objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: SCZN-MNT referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
... sorry that i have created two mnt objects. i had intended that i can update the old mnt object.
can you change please all objects with "sczn-db-mnt" links to SCZN-MNT.
after this, can you delete please the old mnt object sczn-db-mnt from the ripe-db.
many thanks and sorry for my mistake.
kind regards,
andreas schneider de.sczn lir staff
+49 431 7171 5152

Hi, Andreas, you can change the allocated PA through the LIR portal. For all other operations you can use the roboter. For your information, the LIR portal is so well done by the RIPE, that you can do everything there as LIR without contacting the RIPE. And it's very usefull. The LIR portal registration takes about 3 minutes. If you need further help e.g. in german, you can contact me directly. Regards Oliver Notka Ettel GmbH Coburg Alias [NGZ]Gulibert System Admin Network Engineer Sonntagsanger 1 96450 Coburg tel : 09561-871145 fax : 09561-871146 RIPE: ON99-RIPE RIPE-AS: AS13301 x-ncc-regid: de.ettel -----Ursprüngliche Nachricht----- Von: db-help-admin@ripe.net [mailto:db-help-admin@ripe.net] Im Auftrag von Denis Walker Gesendet: Donnerstag, 11. November 2004 11:08 An: Koepp, Karsten Cc: 'andreas_s'; db-help@ripe.net Betreff: Re: help on maintainer object Koepp, Karsten wrote:
Hello Andreas,
I am reading this by accident. Seems, you have already done your job. You should be able to simply delete the old maintainer yourself, as there is no object refering to the old mnt:
It is still referenced: $ whois -r -i mb,ml,md,mr,mu sczn-db-mnt % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html inetnum: 217.150.144.0 - 217.150.159.255 netname: DE-SCZN-20040616 descr: t-systems cds gmbh descr: PROVIDER Local Registry country: DE org: ORG-tcg2-RIPE admin-c: as3037-ripe tech-c: as3037-ripe status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-lower: sczn-db-mnt mnt-routes: sczn-db-mnt notify: lir@sczn.de changed: hostmaster@ripe.net 20040616 source: RIPE mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE As this is an allocation object you will need to contact hostmaster@ripe.net and ask them to change the mnt-lower: and mnt-routes: to your new maintainer and then you will be able to delete your old maintainer. Regards Denis Walker RIPE NCC
11/11/04 10:47:06 whois -imb sczn-db-mnt@whois.ripe.net
whois -h whois.ripe.net -imb sczn-db-mnt ... % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
I guess, you will have to do this in two steps, first change the mnt of the old object, then delete it.
regards Karsten
-----Original Message----- From: andreas_s [mailto:lir@sczn.de] Sent: Wednesday, November 10, 2004 6:49 PM To: db-help@ripe.net Subject: help on maintainer object
dear colleagues, on this time, in the ripe-db are the following maintainer objects present:
old -->
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
new -->
mntner: SCZN-MNT descr: Maintainer for all SCZN objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: SCZN-MNT referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
... sorry that i have created two mnt objects. i had intended that i can update the old mnt object.
can you change please all objects with "sczn-db-mnt" links to SCZN-MNT.
after this, can you delete please the old mnt object sczn-db-mnt from the ripe-db.
many thanks and sorry for my mistake.
kind regards,
andreas schneider de.sczn lir staff
+49 431 7171 5152

Hi, Andreas, you can change the allocated PA through the LIR portal. For all other operations you can use the roboter. For your information, the LIR portal is so well done by the RIPE, that you can do everything there as LIR without contacting the RIPE. And it's very usefull. The LIR portal registration takes about 3 minutes. If you need further help e.g. in german, you can contact me directly. Regards Oliver Notka Ettel GmbH Coburg Alias [NGZ]Gulibert System Admin Network Engineer Sonntagsanger 1 96450 Coburg tel : 09561-871145 fax : 09561-871146 RIPE: ON99-RIPE RIPE-AS: AS13301 x-ncc-regid: de.ettel -----Ursprüngliche Nachricht----- Von: db-help-admin@ripe.net [mailto:db-help-admin@ripe.net] Im Auftrag von Denis Walker Gesendet: Donnerstag, 11. November 2004 11:08 An: Koepp, Karsten Cc: 'andreas_s'; db-help@ripe.net Betreff: Re: help on maintainer object Koepp, Karsten wrote:
Hello Andreas,
I am reading this by accident. Seems, you have already done your job. You should be able to simply delete the old maintainer yourself, as there is no object refering to the old mnt:
It is still referenced: $ whois -r -i mb,ml,md,mr,mu sczn-db-mnt % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html inetnum: 217.150.144.0 - 217.150.159.255 netname: DE-SCZN-20040616 descr: t-systems cds gmbh descr: PROVIDER Local Registry country: DE org: ORG-tcg2-RIPE admin-c: as3037-ripe tech-c: as3037-ripe status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-lower: sczn-db-mnt mnt-routes: sczn-db-mnt notify: lir@sczn.de changed: hostmaster@ripe.net 20040616 source: RIPE mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE As this is an allocation object you will need to contact hostmaster@ripe.net and ask them to change the mnt-lower: and mnt-routes: to your new maintainer and then you will be able to delete your old maintainer. Regards Denis Walker RIPE NCC
11/11/04 10:47:06 whois -imb sczn-db-mnt@whois.ripe.net
whois -h whois.ripe.net -imb sczn-db-mnt ... % This is the RIPE Whois tertiary server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/db/copyright.html
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
I guess, you will have to do this in two steps, first change the mnt of the old object, then delete it.
regards Karsten
-----Original Message----- From: andreas_s [mailto:lir@sczn.de] Sent: Wednesday, November 10, 2004 6:49 PM To: db-help@ripe.net Subject: help on maintainer object
dear colleagues, on this time, in the ripe-db are the following maintainer objects present:
old -->
mntner: sczn-db-mnt descr: maintainer for all sczn objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: sczn-db-mnt referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
new -->
mntner: SCZN-MNT descr: Maintainer for all SCZN objects admin-c: AS3037-RIPE admin-c: TW975-RIPE upd-to: lir@sczn.de auth: md5-pw $1$3f6QLMHH$LsJhKz6dET9u85AdqBSqt/ notify: lir@sczn.de mnt-by: SCZN-MNT referral-by: RIPE-DBM-MNT changed: hostmaster@ripe.net 20040616 source: RIPE
... sorry that i have created two mnt objects. i had intended that i can update the old mnt object.
can you change please all objects with "sczn-db-mnt" links to SCZN-MNT.
after this, can you delete please the old mnt object sczn-db-mnt from the ripe-db.
many thanks and sorry for my mistake.
kind regards,
andreas schneider de.sczn lir staff
+49 431 7171 5152
participants (4)
-
[NGZ]Gulibert
-
Denis Walker
-
Koepp, Karsten
-
O. Notka, Ettel GmbH Coburg