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 ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Fri Mar 22 13:17:41 CET 2019
On Fri, Mar 22, 2019 at 11:09:24AM +0000, Carlos Friaças via anti-abuse-wg wrote: Dear Carlos, >> 8. "So Legacy holders (resources with a legacy status) are for obvious >> reasons, excluded for penalties and out of reach. Also according to the >> policy that specifies services to Legacy holders, as this policy doesn't >> state that it wants to include and impact legacy holders." > > I don't agree. If you check i was one of the co-authors of 2012-07 :-) > In my initial drafts for 2019-03, there was a line about legacy holders. It > seems now clear it needs to be recovered for version 2.0 :-) Although I have mixed feelings about this policy and haven't made my mind yet, I wish you good luck with that one thing. Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
- 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 ]