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] Re: [policy-announce] 2010-08 New Policy Proposal (Abuse contact information)
- Previous message (by thread): [anti-abuse-wg] Re: [policy-announce] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-09 New Policy Proposal (Frequent Update Request)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tobias Knecht
tk at abusix.com
Tue Nov 9 13:36:07 CET 2010
Hi, >> This gives more flexibility to the ISPs. Think about business ISPs >> delegating a /24 to a customer and this customer wants to do his own >> abuse handling. Yes such customers really exists ;-) Today this is a >> huge problem and creates more trouble for NOCs than helping them or >> their abuse department. > > I'm pretty much sure that a lot of LIRs will make a script to create irt > objects basing on actual whois data. That's why and because there are so > many inetnum objects in the DB I have mixed feelings about that > proposal. Even if they do, there will be an enhancement. At the moment there are query restrictions, which are causing problems we can solve with the IRT. And we can solve the problem of variety and confusion on how to do it right. The problem of data accuracy which your concern is aiming to, (I guess) will be handled in another proposal, for example with an mechanisms to report wrong whois information and RIPE NCC enforcing the correctness. > I think that we can do something bit different - we can make irt objects > mandatory for new object types (INET-REG, INET6-REG and AS-REG). Of > course if those new object types will be eventually implemented. I'm absolutely on your page, but we do not know if, and when they are coming and therefor we should work on a solution for the existing things. Thanks, Tobias abusix.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/anti-abuse-wg/attachments/20101109/965f9b16/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] Re: [policy-announce] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-09 New Policy Proposal (Frequent Update Request)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]