Slashdot Mirror
Researchers Suggest P2P As Solution To Video Domination of The Internet
JPawlak writes "NewScientistTech reports that big businesses may be realizing the benefits of P2P technologies. Blizzard uses it to distribute patches for World of Warcraft, and now researchers at Microsoft are indicating internet users may have to use it to help distribute online video clips. The growing cost associated with delivering such content may be becoming prohibitive for some companies. 'The team also suggest a way to prevent Internet Service Providers' costs jumping when their users start uploading much more data. The trick is to allow sharing only between people with the same provider, when data transactions are free. That restriction would cut the pool of sharers into smaller groups, meaning MSN's servers would have to do more to fill any gaps in the service. But costs could still fall by more than half, simulations showed.'"
I have no problems at all with not for profit entities using some of my bandwidth to distribute their files.
I have serious problems with a for profit entity like Microsoft or Redhat doing the same.
The first one I call "charity" or "support". The second one I call "leaching", and its not far from "stealing".
If you're a for profit company and you can't afford bandwidth, then you need to find a new line of work. Don't expect your customers to give you freebies unless you're giving them something *good* in return, and something you're not also giving to those who don't share bandwidth.
I want a new quote. One that won't spill. One that don't cost too much. Or come in a pill.
...how do you implement it? Browsers currently have absolutely no support for implementing anything like this. I'm not sure whether it can be done in Flash. Java is so heavyweight that it would probably scare off most people. ActiveX is a no-go. You can't make people install client software either - 99% will never bother to do that. Unless you can make it work out-of-the-box on browsers, it'll not become popular.
And how do you implement P2P streaming? All P2P protocols until now allow peers to send file pieces in non-streamable order.
There is a term in Low German for the feeling I have right now--SchadenGoFuchyourselves.
Don't trust anyone under thirty.
Especially when someone points to the idiots from Redmondia (and other places) that they should stop reinventing multicast again and again. The technology to do what is needed is there, the ability of ISPs to control it so that it is not detrimental to other users is also there. It has been there since the dawn on the Internet. And it is Multicast. From the viewpoint of network design and network operation theory, P2P is nothing, but an extremely lame sorry and sad excuse for Multicast emulation.
Implementing it is solely a matter of minor network tidy-up for most ISPs along with some software updates for the CE devices (where not supplied by the ISP).
By the way, the same methods which are used to control multicast are also valid for P2P services. TTL adjustment down to under 8 will usually cut down the traffic to be solely within an ISP while cutting it down to under 4 will cut it down so it stays within the same RAS device (2 for non-NAT setups). It is also trivial to deliver a correct setting on a per-ISP basis and to autodetect the necessary setting adjustment.
There is no rocket science here and no research to be done. All the tech is already out there. The problem is that the suppliers of P2P services and developers of P2P software deliberately do not want to do this. In fact, they are doing everything they can to steal more service than the ISP is willing to allocate to them. As a result the ISPs have no other choice but to love this and use a big stick to provide the luving to the customer.
Baker's Law: Misery no longer loves company. Nowadays it insists on it
http://www.sigsegv.cx/
I probably did not express my thoughts clear enough. Let's give it another go.
There are two portions to a P2P network - discovery and data fetch. Discovery determines where do you get your data from and fetch is the actual data flow. An ISP can confine a P2P service to its own network by either limiting discovery or by limiting the actual fetches.
The discovery is where the P2P networks lamely emulate a multicast application. They try to determine if a piece of data A is present in any of the surrounding nodes B,C,D,E,F. In order to do that they in the trivial case transmit to each node. In the more modern networks they transmit to hypernodes and get info from there. In either case they try to emulate a multicast network via a tunnel mesh (just the way people try to emulate Multicast on ATM LANE).
Compared to that a discovery mechanism based on multicast with a unicast reply can give you the information on where exactly is the piece which you are interested with one request. There is usually no need for hypernodes either. It just works. Magically. Further to this, you can set your discovery scope to find nodes which are 1,2,3...n hops away by tweaking TTL. Further to this, it is a true P2P network - totally serverless. If you throw in PKI authentication you can also make it as secure as you wish.
Baker's Law: Misery no longer loves company. Nowadays it insists on it
http://www.sigsegv.cx/