42 ms·
> "Multihoming is becoming the norm instead of the exception" Well - at least Multipath TCP spared us from solving that use-case with generalized BPG usage on
by liotier 13y ago
> "Multihoming is becoming the norm instead of the exception"
Well - at least Multipath TCP spared us from solving that use-case with generalized BPG usage on mobile devices. Too bad, it could have been fun - in a way...
- worklogin 13y agoBGP?
- mdergosits 13y agoBorder Gateway Protocol
- windexh8er 13y agoYou likely don't understand "BGP" at a fundamental level. Considering you need a well known and agreed peering agreement - BGP is not designed for use on end-points in any dynamic peering fashion. It is an external "routing" protocol. Hosts leverage "routed" protocols (e.g. IP). But, say, in our fantasy world your iPhone could take a full Internet routing table (it can't). BGP is not designed to deal with very long prefixes (/32 host routes) and in fact most peering agreements will flat out block prefixes longer than a /24 based on policy. BGP on mobile devices would never have been fun and never worked. If each mobile host that came online required BGP around the world to update it's FIB we'd be in a world of hurt (partially because you can't aggregate host routes as you don't know where they're originating transit from). The more routes you add to BGP the worse BGP becomes from a maintainability perspective. TL;DR Don't mention BGP on mobile devices as fun to any network engineer unless you're using the reference as a bad joke.