New object

> The problem as i see it:

Ip addresses do not change a /24 today will be a /24 tomorrow (ok unless its
aggregated) the only differance is which network they are on. People come and go, some
people have a RIPE oject for every job the have held in this industry, netnames change
from one request to another, and so on.

What this object is designed to do is give as best we can a fixed point from which all
IP's assigned to a customer (organization/company) can be grouped to provide an easy
stable place to see all assignments made to a single customer at differant times. We
have some really old customers going back to 1993, our engineers have changed several
times and differant assignments have been made by differant people with both the admin
and tech contact changing in both the customers network and our own. There is no
common point of referance apart from it is still the same company.

I agree with all the arguments about keeping it up to date but that goes for all
objects. and i think it should be the ISP who keeps up to date after all its in our
interest to keep it up to date.

Bottom line is we can assign addresses to a company and track how much we have
assigned easily and reliably (more). I know how to make raw text searches and inverse
lookups but i am not doing the assignment of our address space our less skilled highly
pressured engineers are, and if we can help them to help me and the NCC track
addresses more accuratly all the better.

Regards,


--
------------------------------------------------------------------------
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"
------------------------------------------------------------------------