From: Bill Woodcock <woody@pch.net>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>,
thejoff@gmail.com
Subject: Re: [NNagain] are you Bill Woodcock?
Date: Fri, 19 Jan 2024 08:26:17 +0100 [thread overview]
Message-ID: <7D4F20E7-F4A8-44C2-BDF5-A666CF7C94FB@pch.net> (raw)
In-Reply-To: <FE1FB975-2717-492C-AF86-78B9262C0F40@gmx.de>
> On Jan 19, 2024, at 08:14, Sebastian Moeller <moeller0@gmx.de> wrote:
>> On 18. Jan 2024, at 23:38, Bill Woodcock via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>> So, if one Internet user wants to talk to another Internet user, generally they hand off their packet to an Internet service provider, who takes it to an exchange, and hands it off to another Internet service provider, who delivers it to the second user. When the second user wants to reply, the process is reversed, but the two Internet service providers may choose a different exchange for the hand-off: since each is economically incentivized to carry the traffic the shortest possible distance (to minimize cost, speed x distance = cost), the first ISP will always choose the IXP that’s nearest the first user, for the hand-off, leaving the second ISP a longer distance to carry the packet. Then, when their situations are reversed, the second ISP will choose the IXP nearest the second user, leaving the first ISP to carry the packet a longer distance.
>
> I would propose a slight modification, "each is economically incentivized to carry the traffic the shortest possible distance" is not free of assumptions... namely that the shortest path is the cheapest path, which is not universally true.
Correct. That’s a simplification of a complex field where distance and cost are frequently intermingled, and routing decisions are typically based on latency, overridden by cost as a matter of policy. However, in a simplified or idealized case, if speed is held constant, distance and cost scale together, so they are usually held to be interchangeable in decision-making in the general case. Speed x distance = cost.
> My personal take is "routing follows cost" that is it is money in the end that steers routing decisions
Yes, exactly.
The primary case in which routes follow a cost that differs from distance is in the preference for distant downstream transit over nearby peers, and distant peers over nearby upstream transit. Though it’s uncommon in networks of small geographic scale, most global-scale networks do this, and it’s the cause of many routing problems and loops.
> ...at least once we include paid peering...
That’s a marketing euphemism for transit.
> My ISP aggregates its customers in a handful of locations in Germany, Hamburg in my case while I actually live a bit closer to Frankfurt than Hamburg, so all traffic first goes to Hamburg even traffic to Frankfurt (resulting in a 500-600 Km detour), I assume they do this for economic reasons and not just out of spite ;)
Essentially all mobile network operators do this. It’s generally a matter of incompetence and lack of competition, rather than spite or economic reasons.
> Now, maybe the important point is, this does not involve IXPs so might be an orange to the IXP apple?
Yes, only indirectly. Most of what you’re discussing involves non-optimal outbound IXP selection, one quarter of the round-trip path. Very real issues, but not anything an IXP or receiving-side ISP can do much about without second-guessing routing decisions to an impractical degree.
-Bill
next prev parent reply other threads:[~2024-01-19 7:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 21:51 le berger des photons
2024-01-18 22:38 ` Bill Woodcock
2024-01-19 1:56 ` Dick Roy
2024-01-19 2:14 ` Bill Woodcock
2024-01-19 3:03 ` Dick Roy
2024-01-19 3:12 ` Dave Crocker
2024-01-19 4:38 ` le berger des photons
2024-01-19 8:36 ` Bill Woodcock
2024-01-19 9:01 ` Frantisek Borsik
2024-01-19 9:03 ` Frantisek Borsik
2024-01-19 11:38 ` le berger des photons
2024-01-19 20:18 ` rjmcmahon
2024-01-21 19:08 ` Joe Williams
2024-01-21 23:14 ` Bill Woodcock
2024-01-23 9:06 ` le berger des photons
2024-01-23 9:23 ` Frantisek Borsik
2024-01-19 7:14 ` Sebastian Moeller
2024-01-19 7:26 ` Bill Woodcock [this message]
2024-01-19 7:51 ` Frantisek Borsik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7D4F20E7-F4A8-44C2-BDF5-A666CF7C94FB@pch.net \
--to=woody@pch.net \
--cc=moeller0@gmx.de \
--cc=nnagain@lists.bufferbloat.net \
--cc=thejoff@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox