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]/
[mat-wg] [atlas] Proposal for public HTTP measurements
- Previous message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
- Next message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Tue Jan 13 23:41:29 CET 2015
> On Jan 13, 2015, at 5:28 PM, Daniel Karrenberg <daniel.karrenberg at ripe.net> wrote: > > sisi, > > <candid> > > ripe atlas was built for monitoring the infrastructure. the direction you are suggesting bears a significant risk of destroying ripe atlas because we will be regarded as breaking our agreement with probe hosts and probe hosts will disconnect their probes. i am opposed to risking ripe atlas for the sake of the http measurements; specifically meaurements that are bound to make ripe atlas a target. i am all for doing the work you suggest, but i have to suggest that you find people willing to cooperate while knowing the consequences. if we proceed like you suggest we may very well end up with no useful platform for any purpose. Perhaps this is a good use-case of having a ‘hosted VM’ type probe? The NLNOG RING is an example of something where it’s a pure full-mesh community but without credits. If there was something like a software probe, i could ask our systems team to deploy one VM per site we have for these purposes, and it could provide this capability with reasonable constraints. - Jared
- Previous message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
- Next message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]