[atlas] Proposal: Generic HTTP measurements [GENERIC-HTTP]

Dear Robert,
As I have expressed at other times, I think we have to be very careful
with enabling HTTP probes due to traffic increase issues.

I have personally delivered quite a few probes to remote locations
in regions with very poor connectivity, and the host's first concern
is how much bandwidth the measurements take up. I have always reassured
them that these are only network level connectivity measurements, and
no web traffic. It seems to me that in the first world it may be
difficult to imagine places where a few megabytes per month of traffic
matters, but that is the case in remote regions, and I think the
benefit of having an Atlas network with worldwide coverage is greater
than being able to perform higher layer measurements or monitoring.

It seems to me that the idea of making it "opt-in" with a tag on the
probe is the right one, even if it makes its deployment and usability
slow at first. I sincerely believe we have a responsibility to hosts
that currently help in complex regions.

Thanks and regards,

Hugo Salgado
NIC Chile - .CL

On 15:03 14/12, Robert Kisteleki wrote:
> Dear RIPE Atlas users,
> 
> We recently published a RIPE Labs article containing a few proposals:
> https://labs.ripe.net/author/kistel/five-proposals-for-a-better-ripe-atlas/.
> We'd like to encourage you to express your comments about this proposal (if
> you'd like to share them) here.
> 
> Regards,
> Robert Kisteleki
> For the RIPE Atlas team
> 
> -- 
> ripe-atlas mailing list
> ripe-atlas at ripe.net
> https://mailman.ripe.net/
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20221216/e4c2b03f/attachment.sig>