Jump to content

Pondering different use of protocols


NoCashBob

Recommended Posts

I wll admit right off the bat that I have no real-world knowledge of protocol design. I intend on getting a few good ebooks on the subject, but as it stands I'm just pondering. If what I'm saying is very unfeasible let me know, but please let me know why that is in as much detail as you wish.

What I've been wondering lately is why a p2p client couldn't be designed to use existing protocols in an unintended manner? I'm sure the overhead would be high, but even 30% of 500KBps is still 150KBps, much better than 30.. Add to then previous the thought that such a client would be near impossible to filter with anything aside from the mightyest of DPI solution, which I'd imagine would have a godzilla sized resource requirement giving the worst of diminishing returns to the ISP.

A second problem with this solution would be how intensive it could be having the software do the work at user level for each packet a protocol should be at OS level. I'm sure some compromise could be reached.

Could your imaging though, the ISPs outrage at a Torrent style p2p running on unencrypted HTTP traffic? There's no way they could run the deep packet inspection on ALL http traffic contents. besides being a breach of privacy (they'd need to inspect the actual contents) the resource overhead for them would be insane! Imagine if the standard HTTP traffic were to have the contents themselves encrypted, but leave the protocol alone? They'd need to breach privacy, and perform very deep DPI on evry http packet on the network.

Anywho, it's a great though, but I'm sure there are many reasons why this might not be workable, but you never know. I'll have to hunt don't some ebooks on protocols design now, I'm suddenly very interested again, lols.

Link to comment
Share on other sites

ebooks on bittorrent?? Fascinating. If you want to learn, read. http://bittorrent.org is official, http://wiki.theory.org has some more info for a starting point.

... Don't know what you mean about existing protocols in an unintended manner... If you wanted to make a post about protocol, one post in protocol discussion would suit much better than two posts. Bittorrent has the capability for handling HTTP urls now as Firon says, with any client (such as uT) which handles webseeds.

Link to comment
Share on other sites

I was thinking more along the line of the data being transfered between peers as being in the form of forged HTTP packets rather than the existing protocols, not http urls for the info files. A forged HTTP packet would appear to be everyday web traffic to DPI, but being forged, could contain CLient usable data in the data portion instead.

This topic and my other post are two very different ideas, so I used two posts. imple as that. Thanks for the post though, I'll check out the wiki on theory, although I thinking more along the lines of protocol development in general.

Cheers

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...