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? ATB, -C. On 07.06.2021 11:09, Edward Shryane via db-wg wrote:
Dear colleagues,
In Remco van Mook's presentation to the Address Policy WG at RIPE 82: "What Colour Is My IP(v4) space? PI Addresses and LIRs", he pointed out that resource "status:" attribute values may not always be all UPPERCASE.
This is because the RIPE database is case-insensitive and case preserving in general, meaning a "status:" attribute value is the same regardless of the case.
However, this may make parsing this value more difficult as the case should be ignored.
Should the DB team implement a rule to always force the "status:" attribute value to uppercase, for consistency?
Regards Ed Shryane RIPE NCC