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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Previous message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Hartmann
richih.mailinglist at gmail.com
Wed Nov 10 02:11:04 CET 2010
On Tue, Nov 9, 2010 at 16:45, Denis Walker <denis at ripe.net> wrote: > We have already weakened its main purpose by making the above attributes > optional. For Incident Response Teams these should be mandatory > attributes. Now they are required attributes, but as we cannot > distinguish between the two different roles this object now serves we > cannot enforce this requirement. If we loosen the requirements any > further for the IRT object it will no longer serve its original purpose. According to the technical howto [1] the irt object already has a concept of trust levels, albeit as a remark. Formalizing a level attribute would allow unverified mostly-optional irt objects to exist in parallel to unverified mostly-required and trusted introduction all-required ones. Richard [1] http://www.ripe.net/db/support/security/irt/irt-h2.html
- Previous message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]