A police records bureau hardens its civic Internet edge. Which inbound eBGP practice best matches filtering bogon and unallocated space?
Select an answer to reveal the explanation.
Short Explanation
Bogon filtering is the nightclub bouncer at the civic edge: private, reserved, and unallocated prefixes don’t get a stamp. Don’t take a full table on faith—check the guest list on the way in.
Full Explanation
Inbound eBGP filtering should drop martians, bogons, and unallocated space that must never appear as valid Internet routes toward the civic network. Combining prefix lists with IRR/RPKI-informed policy strengthens provenance checks beyond crude AS-path length heuristics. Accepting an unfiltered full table increases exposure to spoofed and garbage prefixes. Disabling BGP scanning does not implement bogon policy.