This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] "status:" attribute values in the RIPE database

Next message (by thread): [db-wg] "status:" attribute values in the RIPE database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Mon Jun 7 11:09:31 CEST 2021

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

Next message (by thread): [db-wg] "status:" attribute values in the RIPE database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]