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] NCC still enforcing descr: content
- Previous message (by thread): [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 ]
Tim Kleefass
tim at haitabu.net
Fri Jul 31 08:56:42 CEST 2015
Hi Tim et al, On 28.07.2015 18:01, Tim Bruijnzeels wrote: > Option a: Leave existing cases, "descr:" mandatory, update request forms > ======================================================================== > > We would leave existing cases, but note that this can lead to confusion because the names left there will start to differ from the names in the referenced organisation objects - which are enforced by RIPE NCC. It may not be clear to users where to look for this information and where to change it. And it may lead to situations where people wrongfully assume that the RIPE NCC is still enforcing the "descr:" line. > > We would also need to change request forms and processes to make sure that a sensible description is provided (i.e. not the name). This would take some time to implement, but can be done if this is where we need to go. I like the part "Leave existing cases". Looking at different inetnums it seams good to have a "descr:" tag beside the "netname:", but I don't have a strong opinion on that. Cheers, Tim
- Previous message (by thread): [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 ]
[ db-wg Archives ]