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] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Fri Apr 19 16:52:48 CEST 2019
They had a fiduciary duty not to hand out whole /14s of v4 space to snowshoe spammers set up as eastern european LIRs not too long back They would now as well if such duty wasn't abdicated each time The duty doesn't magically go away of course even if it is abdicated and denied --srs ________________________________ From: anti-abuse-wg <anti-abuse-wg-bounces at ripe.net> on behalf of Nick Hilliard <nick at foobar.org> Sent: Friday, April 19, 2019 8:16 PM To: Carlos Friaças Cc: Gert Doering; anti-abuse-wg at ripe.net Subject: Re: [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation) Carlos Friaças via anti-abuse-wg wrote on 19/04/2019 15:03: > Would you find reasonable to have the rule/policy in place say for 2 or > 3 years, and then evaluate its impact/efectiveness...? No. In principle, the proposal is completely broken, antithetical to the RIPE NCC's obligations of being an address registry and Randy was right to point out that it is a proposal for a kangaroo court. We don't need to make the mistake of testing it out to make sure. It will not have any material impact on hijacking; there are better ways of handling hijacking and the proposal will have a wide variety of serious but unintended side effects, some of which have been raised on this mailing list. And it's unimplementable - the board of the RIPE NCC would have a fiduciary duty to refuse to implement it. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20190419/542f2dc5/attachment.html>
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]