Hi Carsten,
On 7 Jun 2021, at 12:57, Carsten Schiefner <carsten@schiefner.de> wrote:
Ed & all -
makes sense to me, too.
However: Instead of forcing this on the creator/updater of an object - how about the NCC to be as liberal as possible (John Postel's law, the robustness principle) and to accept any case combination, e.g. "aSSigNED pi", but very conservatively keep the attribute sored in the DB in uppercase only?
I agree, apologies I wasn't clear, by force the "status:" attribute value to uppercase, I mean that the value should be automatically changed to all-uppercase, and we should still accept the value in any case. Also, we should perform a cleanup on currently inconsistent values (affecting less than 1% of total inetnum and inet6num objects). Regards Ed
ATB,
-C.