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/[email protected]/

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

• Previous message (by thread): [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 ]

Carsten Schiefner ripe-wgs.cs at schiefner.de
Mon Jun 7 17:31:15 CEST 2021

Thanks, Ed -

this:

On 07.06.2021 14:24, Edward Shryane via db-wg wrote:
> [...]
> 
> 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).

entirely clarifies it.

ATB,

	-C.

• Previous message (by thread): [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 ]

[ db-wg Archives ]