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] 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 ]
Carlos Friaças
cfriacas at fccn.pt
Thu Mar 21 11:38:23 CET 2019
Thanks for the input! Trying to "retouch" 5.0: ======== 5.0 Retroactivity Only hijacking events that occur after this policy has been implemented are eligible to be considered. Evidence older than 18 months (counted from the date where a report is filed) should be disregarded by experts. ======== Best Regards, Carlos On Thu, 21 Mar 2019, Piotr Strzyzewski wrote: > On Thu, Mar 21, 2019 at 09:18:02AM +0000, Carlos Friaças wrote: > > Dear Carlos, > >> What would be reasonable for you? >> >> 2 or 3 years before the date when the report is filed? > > I was thinking more about weeks not years. Mostly due to the nature of > the incident(s) itself. However, I'm not strongly opposed to 2y term. > > 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 ]