[db-wg] NCC still enforcing descr: content

Hello

Since the NCC still seems to heavy-handedly revert changes to descr: in AUT-NUM, INETNUM and INETNUM6 I’m wondering what the current status of the implementation mentioned by Tim in a post to this list from February is:

https://www.ripe.net/ripe/mail/archives/db-wg/2015-February/004496.html

Quote:
-----------------------------------------------------------
"> When will this change go into effect?

We were thinking of mid April, for two reasons:

1) This gives the working group enough time to comment.

2) While the RIPE NCC has finished the effort to ensure that the org-id (and name) are set up correctly for all INETNUM and INET6NUM objects, we are still finalising this work for AUT-NUM objects. We expect that we will finish this effort in about 6 weeks. For consistency it would be easiest to change this for all resource types simultaneously."
-----------------------------------------------------------

I personally know a case where the NCC went as far as to ignore German “umlauts” in the name and deliberately spell it wrong in the descr: field of the guy’s AUT-NUM object. When he tried to set it right (ae (ä) instead of a), the NCC reverted the change. Then there’s a case where someone tried to remove his middle name from the descr: field —> reverted.

Another post on the same subject:
https://www.ripe.net/ripe/mail/archives/members-discuss/2015-June/001737.html

Looks like there’s still a lot of energy wasted in those descr fields now that the org pointer is mandatory.

Cheers