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]/
[anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
- Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kostas Zorbadelos
kzorba at otenet.gr
Tue Nov 29 08:41:45 CET 2011
Leo Vegoda <leo.vegoda at icann.org> writes: > > However, I would suggest that if you want > a data maintenance process to apply to the abuse-c object, then you > should describe it. As you seem to want the RIPE NCC to remove the > registration of address space if abuse-c's are not maintained > appropriately, the standards required should be explicit and either > included in the policy text or referenced by it. > I think this is a valid argument. The proposal should contain the desired outcome as clear and explicitly as possible. And I don't think the desired outcome is to just have a role or person object referenced as the abuse contact, but to actually have abuse contacts. -- Kostas Zorbadelos twitter:@kzorbadelos http://gr.linkedin.com/in/kzorba ---------------------------------------------------------------------------- () www.asciiribbon.org - against HTML e-mail & proprietary attachments /\
- Previous message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
- Next message (by thread): [anti-abuse-wg] 2011-06 New Policy Proposal (Abuse Contact Management in the RIPE NCC Database)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]