17 Dec
2019
17 Dec
'19
10:03 p.m.
In message <SG2PR03MB405349DB2EB23C31B9EF12CCF5500@SG2PR03MB4053.apcprd03.prod.outlook.com>, Suresh Ramasubramanian <ops.lists@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