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] 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 ]
Marco Hogewoning
marcoh at marcoh.net
Wed Nov 10 15:02:36 CET 2010
> I agree with Tobias point on this. From what I read in the proposal I didn't > understand that anything will be deleted, or any current information get > lost. It is just a direction, that in the long run will result in publishing > abuse contacts in a sigle well defined way. Well as you can make sure new objects can't contain abuse-mailbox, you can't easily prevent them from using remarks. So it comes down to education. Educating the maintainers will a hard task, but might be achievable. Educating the users is much harder, this was the problem back in 2007 and it's still the case. This proposal doesn't change anything on that point. >> 1) Poor data quality regarding points of contact >> 2) The fact that there are multiple places people store this info > > Having said this, of course the proposal addresses the point no2. For the data > quality a first step is the 2010-09 proposal from what I understand. Yups, but as these are 2 seperate proposals so no guarantee they both make it and if they do still you run the risk that 008 will lower the data quality that 009 is trying to fix and the net result might be things stay the same. What we need is education, you want people to think about it and start using IRT voluntarily. Kills two birds with one stone, when it's there it's good and people are likely to do what you want. If it isn't there you can always try and resort to other means to find a contact And at the same time you want to make this mechanism clear to the people using the database. And maybe create an API that makes this available and try to persuade people to start using them. It's easy to force maintainers to create an IRT, but it won't get you anywhere when people don't use it. All you get is a load of extra objects with no guarantee the data is of any quality or that the people behind it (if any) will respond and do the right thing. But I am on repeat right now. Groet, MarcoH (no hats)
- 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 ]