It seems as though someone has decided to run a process of 'tidying up' in the RIPE db by fiddling with descr fields. I've been informed that: === During one of our data consistency checks, we saw that the resource holder information for these resources is not consistent: x.x.x.0-y.y.y.255 We will therefore be updating the resource holder information in the RIPE database objects to <company> and ORG-xxxx-RIPE on 2015-06-08." === This is somewhat mysterious, vague and puzzling Confusing because all the relevant handle and organisation records point to the correct objects for this block. Upon asking NCC what they are doing, I'm told that the descr field is incorrect and will be amended, actually to remove from it "London". What on earth is the point of this whole exercise? This has generated confusion on my part and a waste of support resource in NCC to deal with my query. We already have admin, tech and org fields that point to the identifying organisation for the object but now someone has decided that the descr field must have duplicated information. The help section in whois mentions nothing about what data is to be in descr field, nor do I recall any mandate that it must be set to the name of the organisation. I can't be the only one confused by this vague change and asking NCC what is going on and why. Summary: seems a totally pointless waste of time. I guess someone in NCC was bored because I can't see any other point of this. Regards, Paul. -- Paul Civati <paul(at)racksense.com> 0870 321 2855 Rack Sense Ltd - Managed Service Provider - www.racksense.com