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] FW: [aa-wg-chair] Draft Anti-Abuse WG Minutes from RIPE 79
- Previous message (by thread): [anti-abuse-wg] FW: [aa-wg-chair] Draft Anti-Abuse WG Minutes from RIPE 79
- Next message (by thread): [anti-abuse-wg] FW: [aa-wg-chair] Draft Anti-Abuse WG Minutes from RIPE 79
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Tue Dec 17 22:03:17 CET 2019
In message <SG2PR03MB405349DB2EB23C31B9EF12CCF5500 at SG2PR03MB4053.apcprd03.prod.outlook.com>, Suresh Ramasubramanian <ops.lists at gmail.com> wrote: >Ruediger has a nice full list of all the other ways a prefix can be mis- >announced or route leaked. Typos, incompetence in setting up load balancers, >so on and forth. However, the number of these that are malicious and that'd >be of interest to the AAWG... Just to clarify, the set of things that might be of interest to me personally is likely to be somewhat larger than the set of things that might be of interest to the AAWG. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] FW: [aa-wg-chair] Draft Anti-Abuse WG Minutes from RIPE 79
- Next message (by thread): [anti-abuse-wg] FW: [aa-wg-chair] Draft Anti-Abuse WG Minutes from RIPE 79
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]