I really like the sound of these tools, unfortunatley I foresee these tools being used in a malicious manner as well. Without knowing more about the tools, I would say they could also be used to by attackers to footprint their marks.
http://www.measurementlab.net/measurement-lab-tools says "Not Found
The requested URL /measurement-lab-tools was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.8b FrontPage/5.0.2.2635 mod_auth_passthrough/2.1 mod_bwlimited/1.4 PHP/5.2.5 Server at www.measurementlab.net Port 80"
It would be extremely useful to understand more about how these tools actually work.
On the surface they seem like the ycould be useful but one obvious concern is how often they yield a false positive.
How do the tools determine exactly what is happening end to end between a browser and a server?
For that matter what problems can these tools find on a server hosting an application? Can content providers be called out too??
There is a home network (or business network), access network, backbone, perhaps several networks that are transited, a hosting facility, etc etc.
How do we know a particular measurement is not biased. Good researchers always try to minimize that effect but it is a natural human tendency to want to get the reulst you want to see. The best way to avoid this is rigorous peer review.
have service providers gotten the opportunity to vet these tools to verify there is no bias? How do the tools determine that there is not a network/equipment problem versus a provider "blocking bit torrent".
There is a strong tendency these days to shoot first and ask questions later. Take a look at the comments to this blog posting - the tendency was to assume the provider was blcoking access to your site (how ridiculous) when it appears the site may have been overloaded,
If a provider is unfairly implicated for blocking and the firestorm starts the damage is done. Subsequent attempts to remedy the situation tend not to get the same publicity as the initial news.
I really like the sound of these tools, unfortunatley I foresee these tools being used in a malicious manner as well. Without knowing more about the tools, I would say they could also be used to by attackers to footprint their marks.
ReplyDeletePerhaps my ISP is blocking this?
ReplyDeletehttp://www.measurementlab.net/measurement-lab-tools says
"Not Found
The requested URL /measurement-lab-tools was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.8b FrontPage/5.0.2.2635 mod_auth_passthrough/2.1 mod_bwlimited/1.4 PHP/5.2.5 Server at www.measurementlab.net Port 80"
ED
my ISP blocks the site
ReplyDeleteevery time I go there I get "The connection to the server was reset while the page was loading"
It would be extremely useful to understand more about how these tools actually work.
ReplyDeleteOn the surface they seem like the ycould be useful but one obvious concern is how often they yield a false positive.
How do the tools determine exactly what is happening end to end between a browser and a server?
For that matter what problems can these tools find on a server hosting an application? Can content providers be called out too??
There is a home network (or business network), access network, backbone, perhaps several networks that are transited, a hosting facility, etc etc.
How do we know a particular measurement is not biased. Good researchers always try to minimize that effect but it is a natural human tendency to want to get the reulst you want to see. The best way to avoid this is rigorous peer review.
have service providers gotten the opportunity to vet these tools to verify there is no bias?
How do the tools determine that there is not a network/equipment problem versus a provider "blocking bit torrent".
There is a strong tendency these days to shoot first and ask questions later. Take a look at the comments to this blog posting - the tendency was to assume the provider was blcoking access to your site (how ridiculous) when it appears the site may have been overloaded,
If a provider is unfairly implicated for blocking and the firestorm starts the damage is done. Subsequent attempts to remedy the situation tend not to get the same publicity as the initial news.