In message
,
Suresh Ramasubramanian 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
In message <93666.1576523...@segfault.tristatelogic.com>, Ronald F.
Guilmette writes
>Due to my general ignorance of these matters, I would very much like to
>be shown some real-world and current examples of each of the above three
>alleged problems, i.e.:
>
>*) faked origin ASes
>
>*)
: anti-abuse-wg
Date: Tuesday, 17 December 2019 at 3:16 PM
To: Ronald F. Guilmette , anti-abuse-wg@ripe.net
Subject: Re: [anti-abuse-wg] FW: [aa-wg-chair] Draft Anti-Abuse WG Minutes from
RIPE 79
Unfortunately as far as I am aware he is not on the list, or at least I have
never seen him post
use-wg] FW: [aa-wg-chair] Draft Anti-Abuse WG
> Minutes from RIPE 79
>
> In message
> .prod.
> outlook.com>, Brian Nisbet wrote:
>
> >Ruediger said that... [when] he looks at routing tables, he sees a lot
> >of odd stuff including faked origin ASes, AS paths that ar
In message , Brian Nisbet wrote:
>Ruediger said that... [when] he looks at routing tables, he sees a lot
>of odd stuff including faked origin ASes, AS paths that are not
>technically valid, in RPKI – ROAs for ASNs that should not show up
>for public routing. Looking at RPKI, reputation does not
Folks,
Please see the draft minutes from our WG Session in Rotterdam. If you have any
corrections or objections, could you please let us know ASAP?
Thanks,
Brian
Co-Chair, RIPE AA-WG
Brian Nisbet
Service Operations Manager
HEAnet CLG, Ireland's National Education and Research Network
1st
