nanog mailing list archives
Re: Verizon 701 Route leak?
From: Randy Bush <randy () psg com>
Date: Wed, 30 Aug 2017 13:20:16 +0900
Good use-case for https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-adj-rib-out and snapshot auditing before and after changes. Leak didn't last long but it could have been caught within milliseconds verses minutes via oh sh** alarms.
[ i happen to like bmp, but ... ] if the sender did not have the automation or the mops to not leak in the first place, how well will they apply post hoc detection and repair? if the receiver did not filter, and an tier-1 as-path filter would have sufficed in this case, how well do you think they will be at applying post hoc detection and repair? this was an easily preventable ops failure. but what we will do is go to idr and grow and invent 42 more hacks, kinda like ipv6 transition mechanisms. </snark> randy
Current thread:
- Verizon 701 Route leak? Marcus Josephson (Aug 28)
- Re: Verizon 701 Route leak? Youssef Bengelloun-Zahr (Aug 28)
- RE: Verizon 701 Route leak? Marcus Josephson (Aug 28)
- Re: Verizon 701 Route leak? Job Snijders (Aug 28)
- Re: Verizon 701 Route leak? Julien Goodwin (Aug 28)
- RE: Verizon 701 Route leak? Mikael Abrahamsson (Aug 29)
- Re: Verizon 701 Route leak? Randy Bush (Aug 29)
- Re: Verizon 701 Route leak? Tim Evens (tievens) (Aug 30)
- Re: Verizon 701 Route leak? Randy Bush (Aug 29)
- RE: Verizon 701 Route leak? Marcus Josephson (Aug 28)
- Re: Verizon 701 Route leak? Youssef Bengelloun-Zahr (Aug 28)