RARPSL
join:1999-12-08
Suffern, NY
| reply to TK Junk Mail
Re: Rearranging the deck chairs
said by TK Junk Mail  :said by SuperWISP :This "P4P" nonsense is an attempt to quash legitimate complaints from ISPs that P2P is hogging their resources. But it really does nothing to solve the problem. P2P by its very nature is a way of setting up servers on ISPs' networks, taking their upstream bandwidth without paying for it. And "P4P" does nothing to solve that problem. It is a viable solution for LEGALLY distributed content. But it won't be adopted by those trackers that do nothing but serve up stolen music and movies. And, unfortunately, that still is the largest majority of P2P traffic. This P4P type local peering can be added to generic BT software. All that is needed is to do a WHOIS for x.x.x.x@whois.arin.net (where x.x.x.x is your IPN) and you get back your local net block. For me this would be NETBLK-OOL-4BLK (NET-67-80-0-0-1) 67.80.0.0-67.87.255.255. This would allow my BT program to favor peers with 67.80/16 IPNs and keep the traffic primarily on my ISP's network. I can connect to other ISP's peers (up to my max-peer limit) but will choose local peers over remote peers. I am not sure if there is a way to get a full map of my ISP's Netblocks (so I can add local peers on other Netblocks) but at least this will locate MY Netblock. |
|
TK Junk Mail
Go ahead, make my day
Premium
join:2002-03-03
Margate City, NJ
clubs:
 ·Comcast
| said by RARPSL :This P4P type local peering can be added to generic BT software. All that is needed is to do a WHOIS for x.x.x.x@whois.arin.net (where x.x.x.x is your IPN) and you get back your local net block. For me this would be NETBLK-OOL-4BLK (NET-67-80-0-0-1) 67.80.0.0-67.87.255.255. I think the operative words here are "CAN BE". How many will go to that trouble?
--
My BLOG .. .. Internet News .. .. My Web Page |
|
RARPSL
join:1999-12-08
Suffern, NY
| said by TK Junk Mail :said by RARPSL :This P4P type local peering can be added to generic BT software. All that is needed is to do a WHOIS for x.x.x.x@whois.arin.net (where x.x.x.x is your IPN) and you get back your local net block. For me this would be NETBLK-OOL-4BLK (NET-67-80-0-0-1) 67.80.0.0-67.87.255.255. I think the operative words here are "CAN BE". How many will go to that trouble? That depends. If I were a BitTorrent client publisher, added this support, and advertised this new feature, I can see this capability being used to take the wind out of the sails of the ISPs that claim the P2P uses too much of their Internet Bandwidth. The existence of this feature would be a "meeting the ISP half way" gesture and place the ball into the ISP's court to make a similar gesture (or just shut up and knock off with their anti-P2P rhetoric and shenanigans). |
|
