nanog mailing list archives
Re: Rogue objects in routing databases
From: Stephane Bortzmeyer <bortzmeyer () nic fr>
Date: Mon, 27 Jan 2020 19:03:36 +0100
On Sat, Jan 25, 2020 at 12:06:51AM +0100, Florian Brandstetter <florianb () globalone io> wrote a message of 53 lines which said:
Examples of affected networks are: 193.30.32.0/23 45.129.92.0/23 45.129.94.0/24
Note that 193.30.32.0/23 has also a ROA (announces by 42198). So, announces by AS8100 would be RPKI-invalid. 45.129.92.0/23 also has a ROA. Strangely, the prefix stopped being announced on sunday 26. 45.129.94.0/24 has a ROA and is normally announced. So, if AS8100 were to use its abnormal route objects , announces would still be refused by ROA-validating routers.
Current thread:
- Rogue objects in routing databases Florian Brandstetter (Jan 24)
- Re: Rogue objects in routing databases Job Snijders (Jan 24)
- Re: Rogue objects in routing databases Martijn Schmidt via NANOG (Jan 24)
- Re: Rogue objects in routing databases Florian Brandstetter (Jan 25)
- Re: Rogue objects in routing databases Stephane Bortzmeyer (Jan 27)
- Re: Rogue objects in routing databases Florian Brandstetter (Jan 27)
