Hi I would like to here your comments on the following proposal. After being in an audit and getting a list as long as my arm of broken objects in the DB it turned out that the majority of the objects where pre RIPE and not subject to the same checks. I therefore propose that all inetnums without a status (being pre-RIPE there is no status) should be marked with a new status of PR (Pre RIPE) and therefore be ignored by an audit tool. Also all other objects prior to ripe should be flagged so as to be ingnored in an audit, making it much easier to see what really needs fixing. Your thoughts and comments please. -- ------------------------------------------------------------------------ Stephen Burley "If patience is a virtue, and ignorance is bliss, UUNET EMEA Hostmaster you can have a pretty good life [SB855-RIPE] if you're stupid and willing to wait" ------------------------------------------------------------------------
Hi I would like to here your comments on the following proposal. After being in an audit and getting a list as long as my arm of broken objects in the DB it turned out that the majority of the objects where pre RIPE and not subject to the same checks. I therefore propose that all inetnums without a status (being pre-RIPE there is no status) should be marked with a new status of PR (Pre RIPE) and therefore be ignored by an audit tool. Also all other objects prior to ripe should be flagged so as to be ingnored in an audit, making it much easier to see what really needs fixing.
I'd agree with this. Neil.
Hi, On Thu, Mar 29, 2001 at 02:00:23PM +0000, Stephen Burley wrote:
and not subject to the same checks. I therefore propose that all inetnums without a status (being pre-RIPE there is no status) should be marked with a new status of PR (Pre RIPE) and therefore be ignored by an audit tool. Also all other objects prior to ripe should be flagged so as to be ingnored in an audit, making it much easier to see what really needs fixing.
I see your reasoning - but shouldn't all those "Pre RIPE" be fixed some day? The sooner, the better? So for the sake of database quality, I'd vote against your proposal. Yes, it generates work, and more so for the "good guys" (who have been around for ages), but I consider it as important to get rid of the old cruft, or make sure the database entries are correct. Gert Doering -- NetMaster -- SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
"Gert Doering, Netmaster" wrote:
Hi,
On Thu, Mar 29, 2001 at 02:00:23PM +0000, Stephen Burley wrote:
and not subject to the same checks. I therefore propose that all inetnums without a status (being pre-RIPE there is no status) should be marked with a new status of PR (Pre RIPE) and therefore be ignored by an audit tool. Also all other objects prior to ripe should be flagged so as to be ingnored in an audit, making it much easier to see what really needs fixing.
I see your reasoning - but shouldn't all those "Pre RIPE" be fixed some day? The sooner, the better?
So for the sake of database quality, I'd vote against your proposal. Yes, it generates work, and more so for the "good guys" (who have been around for ages), but I consider it as important to get rid of the old cruft, or make sure the database entries are correct.
But how can you apply RIPE rules to the objects when the objects existed before the rules applied. Surley this would be a way of fixing the porblem? We can not retroactivly apply rules when the rules did not apply so they should be marked as special in some way, to exempt them from the current ruleset. How can you fix them when they do not need fixing as they are not broke, and saying they are broke because they do not fit our criteria now, does not make them broke. I would rather they be marked as exempt, then we can fix them by ignoring them in various processes or including them in special cases.
Gert Doering -- NetMaster -- SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
-- ------------------------------------------------------------------------ Stephen Burley "If patience is a virtue, and ignorance is bliss, UUNET EMEA Hostmaster you can have a pretty good life [SB855-RIPE] if you're stupid and willing to wait" ------------------------------------------------------------------------
Hi Stephen, I did it in the last 2 months: adding ASSIGNED PI to every block is not a big job, and at least the audit tool will produce no errors, except for the asm window, which in my opinion should be set to infinite for these Allocated Unspecified blocks. André ----- Original Message ----- From: "Stephen Burley" <stephenb@uk.uu.net> To: <lir-wg@ripe.net> Sent: Thursday, March 29, 2001 4:00 PM Subject: New Proposal Hi I would like to here your comments on the following proposal. After being in an audit and getting a list as long as my arm of broken objects in the DB it turned out that the majority of the objects where pre RIPE and not subject to the same checks. I therefore propose that all inetnums without a status (being pre-RIPE there is no status) should be marked with a new status of PR (Pre RIPE) and therefore be ignored by an audit tool. Also all other objects prior to ripe should be flagged so as to be ingnored in an audit, making it much easier to see what really needs fixing. Your thoughts and comments please. -- ------------------------------------------------------------------------ Stephen Burley "If patience is a virtue, and ignorance is bliss, UUNET EMEA Hostmaster you can have a pretty good life [SB855-RIPE] if you're stupid and willing to wait" ------------------------------------------------------------------------
----- Original Message ----- From: "Stephen Burley" <stephenb@uk.uu.net> To: <lir-wg@ripe.net> Sent: Thursday, March 29, 2001 4:00 PM Subject: New Proposal | I therefore propose that all | inetnums without a status (being pre-RIPE there is no status) should be | marked with a new status of PR (Pre RIPE) Good idea. | and therefore be ignored by an | audit tool. Also all other objects prior to ripe should be flagged so as | to be ingnored in an audit, making it much easier to see what really | needs fixing. At least for a while, while we launch a community effort to clean up this information in a way that makes it auditable (perhaps under somewhat different rules than objects entered under newer policies) -hph
participants (5)
-
Andre Chapuis -
Gert Doering, Netmaster -
Hans Petter Holen -
Neil J. McRae -
Stephen Burley