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] NCC still enforcing descr: content

• Next message (by thread): [db-wg] NCC still enforcing descr: content

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

Sander Steffann sander at steffann.nl
Mon Aug 3 23:18:09 CEST 2015

Hi,

> option B seems like a cleaner long term fix.

I agree. I think leaving descr: mandatory will lead to confusion. Some descr: will refer to an organisation, some will not, some will refer to a different organisation than org:, and for new objects some content for descr: will have to be invented not because there is any useful information but just because the field is mandatory...

If we clean this up I think we should do it properly.

Cheers,
Sander

• Next message (by thread): [db-wg] NCC still enforcing descr: content

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

[ db-wg Archives ]