avd706
insert annoying animated gif here
Premium
join:2003-02-06
Union, NJ | reply to TKJunkMail
these slides
These slides deserve a topic to themselves |
|
TKJunkMail
Enjoy the sun
Premium
join:2002-03-03
Avalon, NJ
 ·Sprint Mobile Broa..
 ·Comcast
3 edits | said by avd706  :These slides deserve a topic to themselves Comcast also keeps updating info on this topic at this web page:
»www.comcast.net/terms/network/
Especially check out the section of this page with downloads of presentations made on the topic in PDF format.
Also check out links about "traffic optimization" that the IETF is evaluating here:
Application-Layer Traffic Optimization (ALTO) Birds of a Feather (BoF) meetings. Comcast is participating in IETF 72.
»www3.tools.ietf.org/agenda/72/alto.html
And there is a multi-page discussion of Comcast's new technique of throttling here at BBR:
»[Speed] Comcast to throttle individual users; all protocols |
|
DaveNJ
No Fear
join:1999-09-01
New Jersey | This is very common sense what comcast is doing rather then messing with protocols. Throttling connections down temporarily is the answer, to bandwidth hogs. Voip, etc should always be protected. Eventually comcast gets it. |
|
jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
| reply to TKJunkMail
said by TKJunkMail :Also check out links about "traffic optimization" that the IETF is evaluating here: Application-Layer Traffic Optimization (ALTO) Birds of a Feather (BoF) meetings. Comcast is participating in IETF 72. » www3.tools.ietf.org/agenda/72/alto.html There were two good relevant BoFs at IETF 72 a few weeks ago. One was ALTO, as you noted. That did not become a working group yet - there will be a 2nd BoF. ALTO is focused on how to standardize P4P-style optimizations of P2P, such as P4P iTrackers. I'd expect some good content at IETF 73 at the ALTO BoF. The agenda from the 72nd meeting is at »www3.tools.ietf.org/agenda/72/alto.html and you will note we contributed to the requirements document at »www.ietf.org/internet-drafts/dra···s-00.txt .
The other relevant BoF was TANA, see agenda at »www3.tools.ietf.org/agenda/72/tana.html, where we presented (see »downloads.comcast.net/docs/IETF%···cast.pdf). TANA is expected to become an official working group before the 73rd meeting. This is very focused on congestion notification mechanisms, as well as bulk data classes.
JL |
|
