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] Abuse Contact Information - Policy Proposal
- Previous message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Next message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Hogewoning
marcoh at marcoh.net
Mon May 3 17:23:20 CEST 2010
> Is it acceptable for you if this is done when there is an IRT (and require > it to have an IRT before 2013)? I don't think you can 'require it to have an IRT by 2013', there are orphans and stale object, those will not magically will get an IRT attached. But we are getting into details where I think we first have to see where this proposal goes. I merely just pointed out there was a design oversight. Now concerning the proposal, IMHO it won't solve any of the problems. You get less data, but still no guarantee it's there or it's correct. This does not add anything compared to the current model. As a simple and alternative suggestion: Make the abuse-mailbox atrribute mandatory for inetnum and inet6num That was the original proposal at the start of the century when we introduced the abuse-mailbox stuff, by that time there was also a very lenghy discussion on IRT being an alternative. Please refer to the archives of the database working group for records on these discussions. Marco (as a private citizen)
- Previous message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
- Next message (by thread): [anti-abuse-wg] Abuse Contact Information - Policy Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]