Re: NCC#2002069654 HMQUESTION
You are correct to say that you can not remove a maintainer from a <aut-num> object without adding a new one.
The attribute <mnt-by> in the <aut-num> object is mandatory, the AS number AS9179 is part of the <as-block> from the RIPE NCC, and if correct the maintainer <AS9179-MNT> is being maintained by yourselves.
How can I phrase this better ? AS9179-MNT (me / my company) is the current but out-of-date maintainer on an object. Without deleting the object (as it is not relly mine) how can I cease being associated with it ? I (AS9179-MNT) no longer am the maintainer of various objects that really belong to the company X in the UK. My company has not been associated with them or provided services to them for sometime. Is it good and recommended practice therefore for me to just delete the objects - this may affect someones service ? cc'ed to lir-wg in case anyone has a better idea... Petr
Dear Peter, Knowtion Hostmaster Role Account wrote:
You are correct to say that you can not remove a maintainer from a
<aut-num>
object without adding a new one.
The attribute <mnt-by> in the <aut-num> object is mandatory, the AS number AS9179 is part of the <as-block> from the RIPE NCC, and if correct the maintainer <AS9179-MNT> is being maintained by yourselves.
How can I phrase this better ?
AS9179-MNT (me / my company) is the current but out-of-date maintainer on an object. Without deleting the object (as it is not relly mine) how can I cease being associated with it ?
I (AS9179-MNT) no longer am the maintainer of various objects that really belong to the company X in the UK. My company has not been associated with them or provided services to them for sometime.
Is it good and recommended practice therefore for me to just delete the objects - this may affect someones service ?
It depends on the nature of the objects. Deletion of the objects that represent resources that don't exist anymore (non announced routes, non referenced person objects, etc.) means a cleanup and is recommended and appreciated. However in case the resource does exist I would suggest changing the maintenance of this object to the real holder of the resource.
cc'ed to lir-wg in case anyone has a better idea...
Petr
Regards, Andrei Robachevsky DB Group RIPE NCC
Dear Peter, Thank you for your reply. In answer to your questions; * AS9179-MNT (me / my company) is the current but out-of-date maintainer on an * object. Without deleting the object (as it is not relly mine) how can I * cease being associated with it ? You could consider contacting the relevant contacts related to the objects in question. They may have their own maintainer they want to place on the objects, in which case you could send an update with the new maintainer as the mnt-by: attribute. If need be the following URL provides information on the creation of a new maintainer: <Maintainer Creation Procedure> http://www.ripe.net/ripencc/pub-services/db/Maintainer_Creation_Procedure.ht... Please contact me if you require further assistance. Kind regards, Winston Schenkers RIPE NCC On Thu, 11 Jul 2002 17:03:16 +0100, Knowtion Hostmaster Role Account wrote: * > You are correct to say that you can not remove a maintainer from a * <aut-num> * > object without adding a new one. * > * > The attribute <mnt-by> in the <aut-num> object is mandatory, the AS number * > AS9179 is part of the <as-block> from the RIPE NCC, and if correct the * > maintainer <AS9179-MNT> is being maintained by yourselves. * * How can I phrase this better ? * * AS9179-MNT (me / my company) is the current but out-of-date maintainer on an * object. Without deleting the object (as it is not relly mine) how can I * cease being associated with it ? * * I (AS9179-MNT) no longer am the maintainer of various objects that really * belong to the company X in the UK. My company has not been associated with * them or provided services to them for sometime. * * Is it good and recommended practice therefore for me to just delete the * objects - this may affect someones service ? * * cc'ed to lir-wg in case anyone has a better idea... * * Petr *
You could consider contacting the relevant contacts related to the objects in question. They may have their own maintainer they want to place on the objects, in which case you could send an update with the new maintainer as the mnt-by: attribute.
They do not respond. Let us assume that the actual contacts are either 'stupid' or 'hostile'. What then ? Peter
If need be the following URL provides information on the creation of a new maintainer:
<Maintainer Creation Procedure>
http://www.ripe.net/ripencc/pub-services/db/Maintainer_Creation_Procedure.ht ml
Please contact me if you require further assistance.
Kind regards,
Winston Schenkers RIPE NCC
On Thu, 11 Jul 2002 17:03:16 +0100, Knowtion Hostmaster Role Account
wrote:
* > You are correct to say that you can not remove a maintainer from a * <aut-num> * > object without adding a new one. * > * > The attribute <mnt-by> in the <aut-num> object is mandatory, the AS number * > AS9179 is part of the <as-block> from the RIPE NCC, and if correct the * > maintainer <AS9179-MNT> is being maintained by yourselves. * * How can I phrase this better ? * * AS9179-MNT (me / my company) is the current but out-of-date maintainer on an * object. Without deleting the object (as it is not relly mine) how can I * cease being associated with it ? * * I (AS9179-MNT) no longer am the maintainer of various objects that really * belong to the company X in the UK. My company has not been associated with * them or provided services to them for sometime. * * Is it good and recommended practice therefore for me to just delete the * objects - this may affect someones service ? * * cc'ed to lir-wg in case anyone has a better idea... * * Petr *
Dear Peter, The maintainer AS9179-MNT maintains quite a lot of objects in the database. Do you want it removed from all of these or just some of them? Can you let us know which objects you no longer wish to be associated with. Regards Denis Walker RIPE NCC Database Administration On Tue, 16 Jul 2002 10:00:03 +0100, Knowtion Hostmaster Role Account wrote: * > You could consider contacting the relevant contacts related to the objects * > in question. They may have their own maintainer they want to place on the * > objects, in which case you could send an update with the new maintainer as * the * > mnt-by: attribute. * * They do not respond. Let us assume that the actual contacts are either * 'stupid' or 'hostile'. What then ? * * Peter * * > If need be the following URL provides information on the creation of a new * > maintainer: * > * > <Maintainer Creation Procedure> * > * http://www.ripe.net/ripencc/pub-services/db/Maintainer_Creation_Procedure.ht * ml * > * > Please contact me if you require further assistance. * > * > * > Kind regards, * > * > Winston Schenkers * > RIPE NCC * > * > On Thu, 11 Jul 2002 17:03:16 +0100, Knowtion Hostmaster Role Account * wrote: * > * > You are correct to say that you can not remove a maintainer from a * > * <aut-num> * > * > object without adding a new one. * > * > * > * > The attribute <mnt-by> in the <aut-num> object is mandatory, the AS * number * > * > AS9179 is part of the <as-block> from the RIPE NCC, and if correct the * > * > maintainer <AS9179-MNT> is being maintained by yourselves. * > * * > * How can I phrase this better ? * > * * > * AS9179-MNT (me / my company) is the current but out-of-date maintainer * on an * > * object. Without deleting the object (as it is not relly mine) how can I * > * cease being associated with it ? * > * * > * I (AS9179-MNT) no longer am the maintainer of various objects that * really * > * belong to the company X in the UK. My company has not been associated * with * > * them or provided services to them for sometime. * > * * > * Is it good and recommended practice therefore for me to just delete the * > * objects - this may affect someones service ? * > * * > * cc'ed to lir-wg in case anyone has a better idea... * > * * > * Petr * > * * > *
Dear Peter,
The maintainer AS9179-MNT maintains quite a lot of objects in the database. Do you want it removed from all of these or just some of them? Can you let us know which objects you no longer wish to be associated with.
Regards Denis Walker RIPE NCC Database Administration
On Tue, 16 Jul 2002 10:00:03 +0100, Knowtion Hostmaster Role Account wrote: * > You could consider contacting the relevant contacts related to the objects * > in question. They may have their own maintainer they want to place on
* > objects, in which case you could send an update with the new
* the * > mnt-by: attribute. * * They do not respond. Let us assume that the actual contacts are either * 'stupid' or 'hostile'. What then ? * * Peter * * > If need be the following URL provides information on the creation of a new * > maintainer: * > * > <Maintainer Creation Procedure> * > * http://www.ripe.net/ripencc/pub-services/db/Maintainer_Creation_Procedure.ht * ml * > * > Please contact me if you require further assistance. * > * > * > Kind regards, * > * > Winston Schenkers * > RIPE NCC * > * > On Thu, 11 Jul 2002 17:03:16 +0100, Knowtion Hostmaster Role Account * wrote: * > * > You are correct to say that you can not remove a maintainer from a * > * <aut-num> * > * > object without adding a new one. * > * > * > * > The attribute <mnt-by> in the <aut-num> object is mandatory, the AS * number * > * > AS9179 is part of the <as-block> from the RIPE NCC, and if correct
* > * > maintainer <AS9179-MNT> is being maintained by yourselves. * > * * > * How can I phrase this better ? * > * * > * AS9179-MNT (me / my company) is the current but out-of-date
* on an * > * object. Without deleting the object (as it is not relly mine) how can I * > * cease being associated with it ? * > * * > * I (AS9179-MNT) no longer am the maintainer of various objects that * really * > * belong to the company X in the UK. My company has not been associated * with * > * them or provided services to them for sometime. * > * * > * Is it good and recommended practice therefore for me to just delete
No! Please leave everything for the moment... My question was a general one. Once I have the answer - which seems to be the one below - then I will forward requests to be removed as separate requests to hostmaster@ripe.net. It is that simply this situation is not covered in existing RIPE documents - or at least that I have read. Peter ----- Original Message ----- From: "RIPE Database Manager" <ripe-dbm@ripe.net> To: "Knowtion Hostmaster Role Account" <hostmaster@knowtion.net> Cc: <lir-wg@ripe.net>; "RIPE NCC" <ncc@ripe.net> Sent: Tuesday, July 23, 2002 10:07 AM Subject: [lir-wg] Re: NCC#2002069654 NCC#2002069654 HMQUESTION the maintainer as the maintainer the
* > * objects - this may affect someones service ? * > * * > * cc'ed to lir-wg in case anyone has a better idea... * > * * > * Petr * > * * > *
participants (5)
-
Andrei Robachevsky -
Knowtion Hostmaster Role Account -
Peter Galbavy -
RIPE Database Manager -
RIPE NCC