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] 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 ]
Adrian
ripe-wg-antiabuse at kyubu.de
Thu Nov 24 15:23:10 CET 2011
On Thu, Nov 24, 2011 at 03:06:53PM +0100, Tobias Knecht wrote: hi, > If you look at this really old document > http://www.ripe.net/data-tools/db/irt/ripe-irt-object-technical-how-to/#113 > you will find under point 1.1.4 that signature, encryption and auth are > mandatory fields, Yes, I was aware of this document. > which they are not any more today. At least one of > them is not mandatory anymore today. Couldn't find documentation at the > moment. IIRC, TI is the the one and only body to maintain IRT-objects. And, all of the above contraints are still mandatory. (At least they were until 11/2010). Cheers, Adrian
- 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 ]