From owner-lir-wg@ripe.net Thu Mar 29 14:42:22 2001 From: Stephen Burley <stephenb@uk.uu.net>
Stephen,
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 think the idea of marking such inetnums is very good. I am just wondering whether "no status" really means "pre RIPE". I suspect it is not the case, as Daniel's document was discussed on the mailing list in May 1995 (and is dated 30 June 0995), while RIPE NCC did perform allocations much earlier as far as I remember. So my point is that the term "pre RIPE" may be misleading. What about "status: UK"? (UK for UnKnown :)) ) Janos
On Thu, Mar 29, 2001 at 04:33:23PM +0200, Janos Zsako wrote:
What about "status: UK"? (UK for UnKnown :)) )
Janos
UK - United Kingdom -- ------------------------------------------------------- P h i l D u f f e n S y s t e m s M a n a g e r t e l +44 (0)845 333 5000 f a x +44 (0)845 333 5001 e - m a i l phil.duffen@uk.easynet.net -------------------------------------------------------
Janos Zsako wrote:
From owner-lir-wg@ripe.net Thu Mar 29 14:42:22 2001 From: Stephen Burley <stephenb@uk.uu.net>
Stephen,
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 think the idea of marking such inetnums is very good.
I am just wondering whether "no status" really means "pre RIPE". I suspect it is not the case, as Daniel's document was discussed on the mailing list in May 1995 (and is dated 30 June 0995), while RIPE NCC did perform allocations much earlier as far as I remember.
But in a classful enviroment. I agree "no status" does not always mean pre-RIPE but "no status" and an intial date before RIPE interaction does. (Date to be decided by the community)
So my point is that the term "pre RIPE" may be misleading.
What about "status: UK"? (UK for UnKnown :)) )
UK = United Kingdom What about CA = Classful Allocation
Janos
-- ------------------------------------------------------------------------ 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" ------------------------------------------------------------------------
UK = United Kingdom
What about CA = Classful Allocation
CA = Canada ;-) For allocations we've already got 'PA', 'PI' and 'UNSPECIFIED' but only 'PA' or 'PI' for assignments. Why not use the "missing" combination 'ASSIGNED UNSPECIFIED' to "document past allocations with assignments of both types or unknown type"? For most purposes this would have to be treated as being the same as 'ASSIGNED PI' but would allow documentation of such historical entries where it's needed. James
participants (4)
-
James Aldridge -
Janos Zsako -
Phil Duffen -
Stephen Burley