This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] HTTP/HTTPS probe
- Previous message (by thread): [atlas] HTTP/HTTPS probe
- Next message (by thread): [atlas] HTTP/HTTPS probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rodolfo García Peñas (kix)
kix at kix.es
Wed Oct 2 11:21:37 CEST 2013
Robert Kisteleki <robert at ripe.net> escribió: > On 2013.10.02. 10:13, Stephane Bortzmeyer wrote: >> On Tue, Oct 01, 2013 at 08:01:28PM +0200, >> Robert Kisteleki <robert at ripe.net> wrote >> a message of 33 lines which said: >> >>> This topic has surfaced a couple of times already (in this list: Aug >>> 2012, July 2013), probably on other related lists too. >> >> It would surface less often if the doc were fixed >> <https://atlas.ripe.net/doc/udm#creating-a-new-measurement>. > > We updated the doc right after the last time you asked :-) > > "Important note: HTTP(6) measurements are not available to all UDM users; > they are restricted while the potential impact is evaluated." Hi, my proposal: - Two different checks in the probe configuration: - http:// small file download - http:// big file download Then, the user can select if their probe will download big or small files (bw impact). - Fixed targets. The probe can connect only selected hosts and files (privacy impact). IMO, the targets should be non commercial sites, with good bw. Regards, kix > Regards, > Robert Rodolfo García Peñas (kix) http://www.kix.es/
- Previous message (by thread): [atlas] HTTP/HTTPS probe
- Next message (by thread): [atlas] HTTP/HTTPS probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]