funchords
Robb
Premium,MVM
join:2001-03-11
Hillsboro, OR
 ·Verizon Online DSL
 ·Skype
 ·Comcast
edit:
May 25th, @02:39PM
| said by patcat88  :said by funchords :I'm fine with that suggestion as long as the USERS (actually, their apps) decide what packets to give the lower priority markings to. Then Comcast can obey those markings (RFC2474). Way too open to abuse. What if someone decides to mark torrent traffic with a tag used for VOIP? You don't tag by "type" (torrent, VOIP) but by priority (Expedited, Assured, Normal). But your observation and question is still a valid one.
If someone wants to tag their torrents Expedited, that's their business but it's easily solved and its covered in the RFC2474.
ISPs simply need to allocate a certain number of bytes/hr. (or percentage, or per day or however they want to dice it up) as the quota for priority handling, then when that quota gets reached, everything on that account gets the default "best-effort" normal handling.
Some torrent traffic is being watched "in real time" like a streaming video (BitTorrent, Vuze, Pando, and Podcasting are all services that do this). So users would want to tag this kind of download higher than normal background file transfers (but probably not as high as VOIP).
G711 = consumes 90 kbps or around 40MB per hour. So if there was a limit of 200MB of Expedited Forwarding a day, you could talk on the phone for 5 hours without ever hitting the limit. You wouldn't be torrenting very long before you hit that limit. Either way, once the limit is hit, you're not cut off -- you're just not "expedited" anymore.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
HTTP is the new Bandwidth Hog...
|
