Meh... "By default your neighbor just believes you, and doesn't have a really reliable way to tell if you are actually telling the truth" - while this is not 10

Meh... "By default your neighbor just believes you, and doesn't have a really reliable way to tell if you are actually telling the truth" - while this is not 100% true with regard to most peering configurations via tier 1 carriers, there is a slight nugget of truth here. You can't just order a circuit from AT&T/Verizon/Sprint and inject whatever you want. First you have to have an AS assigned to you (if you're to have the ability to announce anyway) and then beyond that it's generally a process of negotiating sane terms of what you're presenting to them and what they're presenting to you (generally as the customer you want the entire table, but there are exceptions). At that point the config on the far end will mimic what was agreed upon (prefixes advertised and general length protections such that you don't spam out thousands of /30s from your transport or something horrid like that). While there is no way to truly validate the authenticity of the update - there is generally a decent chain of custody. BGP is a great playground for injection research. The best part is via looking glass sites it's very trivial to target specific, and core, platforms. That being said... Regardless of BGP itself beyond certificate validation and pinning we should also be doing path checking. I mentioned this to Moxie for a potential addition into Convergence, and from the page: "Convergence trust notaries use network perspective to validate your communication by default, but can be extended to use whatever methods the notary operator would like. This might include DNSSEC, BGP data, "SSL observatory" results, or even CA validation." ...AS path should be looked at more closely in all secure communications we're delivering. It's trivial to get the AS path for the hops and, since it is generally static from known origination networks it would be relatively easy to build history of known AS path order and vet with regionalized crowd-sourcing. Huge path swings should be obvious, today they're not to most. Some good resources are: * Team Cymru - https://www.team-cymru.org/Monitoring/BGP/ https://www.team-cymru.org/Monitoring/BGP/ * Colorado State BGPmon - http://bgpmon.netsec.colostate.edu/ http://bgpmon.netsec.colostate.edu/ * Cyclops (UCLA) - http://cyclops.cs.ucla.edu http://cyclops.cs.ucla.edu ...and there's also BGPMon (the service), but it has turned into a more paid for service (although you can monitor 5 x AS for free). * BGPmon - http://www.bgpmon.net/ http://www.bgpmon.net/