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
>
>*)
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, is much smaller, wouldn’t you say?
Unfortunately as far as I am aware he is not on the list, or at least I have
never seen him post here.
Brian
Co-Chair, RIPE AA-WG
Brian Nisbet
Service Operations Manager
HEAnet CLG, Ireland's National Education and Research Network
1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland
