site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Post a:
Post a:
AuthorAll Replies


jig

join:2001-01-05
Hacienda Heights, CA

reply to espaeth

Re: Let's not leave out the criticisms in Bennet's rewrite

said by espaeth:

said by jig:

he's missing the point. if the management is at the edges of the ISP's network (to reduce their interconnect cost, which is one of their huge issues)
I believe that to be a misread of the situation -- the carrier interconnect costs are minimal compared to the rest of the infrastructure costs.
even if you are right, the infrastructure costs are minimized because the p2p uTP traffic automatically meters itself appropriately IF something isn't already unbalanced in how the system deals with different protocols. regardless of whether you are right about the costs differences, the interconnect costs are what they are choosing to complain about most, lately.

said by jig:

then IF uTP is granular enough to reduce throughput PER PEER (rather than globally for all current torrents), the client will automatically gravitate towards intra-ISP peers, which will reduce costs and extra-ISP congestion.
Even if you sourced 100% of the content from the internal ISP network, you'd have the exact same subscriber access network choke points that you do today.
that's not true unless each DSLAM or cable headnode has unlimited upstream bandwidth. cable might be feeling the bite mostly on upload bandwidth allocated for the full node (250 customers/node?), but that's not the whole story.

as far as the UDP specific stuff goes, UDP is a general encapsulation for custom protocols (and was originally developed as such, including as a testbed for an FTP replacement). rather than talk about what hardware mechanisms there are for UDP control, instead think about what the underlying custom protocol does; in this case, uTP. uTP should take care of congestion issues itself (again, recognizing that "congestion" is built into the protocol or the client application, and not necessarily at the control of the ISP, which may be problematic). finally, have just looked at BGP route reflectors, they seem to be dependent on TCP/IP, but i "think" the initial handshake in uTP is still over TCP. i think once the route is set up, then it can still be used for the UDP traffic. other than that, with the increase in VOIP traffic, ISPs and hardware manufacturers will eventually have to figure out how to manage traffic without relying on TCP alone anyway (or ban all non TCP, which would never be done in the US for any length of time).
--
Catapultam habeo. Nisi pecuniam omnem mihi dabis, ad caput tuum saxum immane mittam.

Thursday, 31-May 07:04:59 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics