On Mon, 25 Feb 2013, Gert Doering wrote:
Hi,
On Mon, Feb 25, 2013 at 10:16:14AM +0000, Nick Hilliard wrote:
The flip side of this argument could be taken as: this holder's interest in maintaining their /16 (i.e. probably infrastructure which is very important to their business) is so small that in a period of 13 years, they couldn't be bothered spending a couple of hours updating the registry details for it.
If everything works, why would they need to even think about it?
Like: still using the same AS to announce it, still using the same set of nameservers - so there was never a need to update anything due to "things not working on the technical side", so I can see why no updates have ever done...
You are on the right path here. The sudden need for updates was caues by a request to change name servers. And it's not 13 years. They got the /16 in 1990. :-)
Our /16 PA allocation is from 1996, and all the updates on the inetnum: are hostmaster@ripe.net in 2002, 2004 and 2010 - and I'd bet all but one of these have been automated due to RIPE DB structural changes. The route: object is unchanged since 2002, since *there have not been any changes*.
So I'm not sure why a PI /16 holder would have more need for updates, if nothing changed...
Exactly. Regards, Daniel Stolpe _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe@resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 13 054 556741-1193 103 02 Stockholm