[nSLUG] traffic shaping and archive networks

George N. White III gnwiii at gmail.com
Sun Nov 23 12:56:23 AST 2008


It seems that traffic shaping is here to stay:

--Canadian Telecom Regulator Says Bell Canada's Traffic Throttling OK
(November 20, 2008)
The Canadian Radio-television and Telecommunications Commission (CRTC)
has denied a complaint filed by the Canadian Association of Internet
Providers (CAIP) asking that CRTC stop Bell Canada from throttling
certain types of Internet traffic.  Bell Canada admits that it has
slowed traffic from peer-to-peer (P2P) filesharing websites during peak
Internet traffic hours.  The company also acknowledged that it uses deep
packet inspection.  CRTC said that "CAIP has not demonstrated that Bell
Canada's methodology for determining congestion in the network is
inappropriate."  The finding contrasts with recent similar issues in the
US involving Comcast's use of selective traffic throttling.
http://www.pcmag.com/article2/0,2817,2335133,00.asp
http://www.theglobeandmail.com/servlet/story/RTGAM.20081120.wcrtc1120/BNStory/Technology/?cid=al_gam_nletter_techweekly

How do you tell the difference between problems caused by conjestion and the
effects of shaping?

Have NSLUG users encountered problems that can be attributed to shaping?

Is shaping causing problems for other archive networks?

The Comprehensive TeX Archive Network is used with a new
package manager, tlmgr, which first downloads a master
database that gives the versions of the packages on the
server,  If you don't get the database and packages from the
same server you can run into difficulties if the two servers
have different versions of some packages.  Thsi can  create
problems for users with unreliable network access.

-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia



More information about the nSLUG mailing list