Blocking port 7 from latency probes...

[Jeff Taylor]

All,

Am I the only one that is getting tired of the latency probes to tcp
port 7 on my dns servers? I have traced it down to DoubleClick.Net
using the app Global Dispatch from Resonate. I tried explaining my
objections to both DoubleClick & Resonate, but they fell upon deaf &
stupid ears. Here is the last e-mail:

>Jeff Taylor wrote:
>> 
>> Rich,
>> 
>> You still do not understand my position.

>Perhaps I can expand-

>> What is my motivation to allow
>> your product to measure latency to my network & not be compensated? As I
>> see it, this data is used by your customers to optimize the delivery of
>> some kind of content.

>We are only doing these measurements based on requests coming from your users.
>If none of your users ever requested any DoubleClick content, you would never see our latency measurements.
>The process benefits both client and server.
>The client recieves the fastest service possible, and the open connection count on the servers is kept to the minimum.

>> After I start blocking your attempts to measure
>> latency to my network, will this impact you accuracy?

>Possibly, depending on what you consider "blocking".

>> If so, the sites
>> running your product will make poor decisions from where to best deliver
>> their content & possibly appear to be slow.

>If our latency measurement fails to determine the best POP, you may be served from a less-than-optimal server.

>> If they continue to appear to
>> be to slow, my users will be reluctant to go to them.

>Exactly, you want your users to have the best experience possible, right?

>> As I see it, nothing
>> affects me. So again, what is my motivation to assist you?

>Your motivation would be to provide your users with the best possible service.
>"Blocking" these measurements would be counter-productive.