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... 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... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279