[oarsinsync]

> You can receive just a default route … You won't lose out on any functionality in dual homing or anything like that.

Except you do lose out on best path routing / any other outbound TE, and you’re now restricted to rudimentary load balancing methodologies / manual prefix-specific hackery.

[jpgvm]

If you aren't multi-homed that doesn't matter at all though.

For a home network I'm guessing you are pretty unlikely to do the multi-homing from the house, more likely you will either just have a single upstream or if you are connecting it into your own collocated infrastructure you will do iBGP and let your actual edge BGP routers handle the multi-homed upstreams and sync the full route table etc.

I was tempted to do this once before when I was running my own hosting company but it was prohibitive cost wise to get the circuit I wanted. :(

[oarsinsync]

> If you aren't multi-homed that doesn't matter at all though.

The parent I was responding to was explicitly claiming no downside to being default-only while multihomed.

[martyvis]

And that's why SD-WAN (software defined wide area network) technology now exists. In a lot of ways it is even better than BGP in that you direct traffic based on performance measurements - either actively through SLA tests or passively watching traffic flows and measuring latency. Using BGP routing based on hop counts and AS paths is akin to following road signs rather than getting live routing that knows traffic for instance from Google Maps

[oarsinsync]

SD-WAN technology also creates a number of new ways for unthinking people to shoot themselves in the foot.

Noction is a wonderful example of this. It has sane defaults, but insane customers, who think that it’s a good idea for them to originate more specifics for other outside networks, because they’ll never leak them outside of their own AS (narrator: of course, the prefixes leaked).

I think the most notable example of this recently was Verizon (the insane customer) using Noction (the SD-WAN technology) and doing exactly that, causing mass traffic disruption as they announced more specifics for other peoples prefixes, drawing all that traffic to their own network instead.

[throw0101c]

> Except you do lose out on best path routing / any other outbound TE, and you’re now restricted to rudimentary load balancing methodologies / manual prefix-specific hackery.

After 3-4 hops you're probably hitting a Tier 1 network, after which point you can basically think of the Internet like cloud icon you see in many diagrams, because your route choices are no longer really determining reachability, rather the choices of other people/companies are:

* https://en.wikipedia.org/wiki/Tier_1_network

If you're talking about reachability of a network on another continent or the other side of the planet, your local decisions aren't going to much to determine the path.

The main thing to have locally for routing decisions is the ASNs/networks of the other customers of your ISPs: if Service A is also a customer of ISP #1, you want to send traffic for them through that service instead of ISP #2.

The other nice thing to have is the reachability to the closest IXP, as quite often many CDNs have connections to those.

Beyond knowing IXP reachability and other-customers reachability, I don't think there are many other advantages for a smaller entity on the Internet, so a full Internet-wide BGP is not needed.

[iptrans]

Only for outbound traffic, tho.

For eyeball networks and other stub networks this is mostly fine.