Earlier quoted context omitted.
Yup, and in Comcast's case, when Netflix finally paid Comcast's ransom, the problem was suddenly fixed a few minutes later, because Comcast literally just had to reconfigure the router and plug in a second cable.
In those days it was typical for the costs of peering to be borne by the sender, relative to the traffic ratio. This changed when Netflix and Youtube decided to use their PR and lobbying strength to bring the negotiation to the court of public opinion - and normal people started referring to typical peering cost-sharing agreements using emotionally loaded words like "ransom"
Peering ratio requirements are kind of a scapegoat. Especially in the case of an 'eyeball' network like Comcast. I have 250Mb down, and 10mb up. (I would love 50Mb up, I push a ton of docker images daily). Their circuits they sell their clients will only re-enforce those ratios.. (then again, if netflix was to partner with a bunch of backup providers, like Mozy, crashplan, backblaze, etc, to carry their backup traffic, that could get VERY interesting)
[0] https://drpeering.net/white-papers/The-Folly-Of-Peering-Rati...