I know the answer to this one! We need these guys to setup at the other end of a Level3 link, and then Verizon customers can push them one byte for each byte they get from Netflix:
Seriously though: what if Netflix worked with Level3 to set up an efficient Level3-owned /dev/null server in the carrier hotel AND have every Netflix client that connects over Verizon upload random bits to that IP address whenever buffering is complete or the movie is paused? Then the rates would balance out, and Verizon would no longer have a contractual excuse to NOT hook up those cables to the Level3 endpoint. The only way for Verizon to mitigate this would be to deny their end users the upstream bandwidth they've paid for but are not using (cue user outcry), or to smear Netflix even more so than they're already doing (cue more chances for the PR to backfire). Verizon would hate Level3 for this, but they already do, and they couldn't do anything about it without denying their end users Netflix access altogether!
Of course, since the NSA would need to listen in on all that new random-bit traffic (since Netflix is obviously the new Skype in the terror playbook), taxes would need to rise significantly in order to pay for more NSA bulk-data-collection servers. But that's just the cost of living in America...
http://devnull-as-a-service.com
Imbalance fixed, but I don't think that is what Verizon wants.