[db-wg] "status:" attribute values in the RIPE database
- Previous message (by thread): [db-wg] Bogon cleanup -- Current anomalies
- Next message (by thread): [db-wg] "status:" attribute values in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Tue Jul 27 15:59:38 CEST 2021
Colleagues The chairs recognise a consensus to force "status:" values to uppercase on updates and for the RIPE NCC to perform a one time update across the database to convert existing "status:" values to uppercase where necessary. We ask the RIPE NCC to go ahead with this process and inform the community of their implementation plans. regards William & denis co-chairs DB-WG On Mon, 7 Jun 2021 at 11:09, Edward Shryane via db-wg <db-wg at ripe.net> 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 > >
- Previous message (by thread): [db-wg] Bogon cleanup -- Current anomalies
- Next message (by thread): [db-wg] "status:" attribute values in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]