P4P is a win-win
Anonymous Coward posts "When you make the API and expect the user-side application to behave, you know what you're calling for... surprise, surpise, the applicaton will ABUSE it! This is a pipe dream..."
The nice thing about P4P is that localizing network traffic is a win-win for both the ISP and the P2P network, so both have a strong incentive to work together.
To illustrate, the test that Pando Networks and Yale ran on Verizon and Telefonica's networks showed that:
- Knowledge of the ISP infrastructure allowed the P2P network to localize network traffic. For example, using random peer assignment,
- Downloading from people near you is much faster than downloading from people at random locations. So P4P downloads were on average 205% faster than P2P downloads.
- Transfers between ISP's dropped by over 50%, meaning that ISP's saved money on external transit (which are a major cost for ISP's), because that data was delivered within the ISP instead.
- Transfers within the ISP were also localized, reduced long distance transit consumption within the ISP network. P2P downloads traversed an average of 5.5 long distance links (e.g. city to city) to get from the seed to the downloader. With P4P, transfers averaged 0.9 long distance links (i.e. consuming much less of the network). To look at it another way, with "random peer" P2P, only 6% of data downloaded within the ISP was from your own metro area. With P4P, that number was a whopping 58%.
Because this is a win-win situation, there's no "abuse", in that nobody "loses" if the other side does too much P4P.
There's more information about P4P at http://www.pandonetworks.com/p4p , and the P4P Working Group at http://www.dcia.info/activities#p4p .
- Laird Popkin, Co-Chair, P4P Working Group (and CTO, Pando Networks)