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] Cleanup work for "abuse-mailbox:" in certain ORGANISATION objects, following policy 2011-06
- Previous message (by thread): [db-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [db-wg] [anti-abuse-wg] Cleanup work for "abuse-mailbox:" in certain ORGANISATION objects, following policy 2011-06
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Bruijnzeels
tim at ripe.net
Thu Mar 3 16:20:18 CET 2016
Dear working group, As you know, the RIPE NCC completed the work for the 2011-06 policy on 15 February, and "abuse-c:" is now added to all organisations that hold resources allocated or assigned by the RIPE NCC. Going forward we propose to: - Remove "abuse-mailbox:" for all ORGANISATION objects that *have* "abuse-c:" in a one-off operation - Introduce a business rule to prevent adding "abuse-mailbox:" to ORGANISATION objects, urging people to use "abuse-c:" instead Please note that the proposal above does not force anyone to use "abuse-c:", it just enforces that "abuse-c:" is used instead of "abuse-mailbox:". Having both attributes on an ORGANISATION object is extremely confusing, and currently updating "abuse-mailbox:" does not work in the LIR Portal organisation object editor. We therefore believe that the cleanup is needed, and we hope that this will not be controversial. We would like to ask the working group for the mandate to do the cleanup proposed above. Originally the intent was to clean up "abuse-mailbox:" on all objects (except in abuse-c roles) and possibly IRT objects. However, we are fully aware that more controversy exists here. There is a lot of discussion about whether "abuse-c:" can be mandatory for organisations holding legacy resources (2016-01). Questions are being raised about the data model. We are following these discussions with interest and we believe that this part of the originally proposed cleanup should be put on hold until we have a more clear direction from those discussions. Kind regards, Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC Database Group
- Previous message (by thread): [db-wg] objection to RIPE policy proposal 2016-01
- Next message (by thread): [db-wg] [anti-abuse-wg] Cleanup work for "abuse-mailbox:" in certain ORGANISATION objects, following policy 2011-06
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]