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] Proposal: Measure well-known CDNs,[CDN-HTTP]
- Previous message (by thread): [atlas] Proposal: Measure well-known CDNs,[CDN-HTTP]
- Next message (by thread): [atlas] Proposal: Measure well-known CDNs,[CDN-HTTP]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Arzhel Younsi
ayounsi at wikimedia.org
Thu Dec 22 15:11:41 CET 2022
Hello! Disclaimer: I work for the Wikimedia Foundation. I see some of the pushbacks on this proposal are about running measurements towards commercial services. One middle ground here might be to run such measurements towards non for profits entities that run their own CDN. Obviously I'm thinking of Wikipedia (and we would be happy to support such a goal) but there might be others as well (eg. Internet Archives). Thanks On Tue, Dec 20, 2022 at 6:00 PM Jared Mauch <jared at puck.nether.net> wrote: > > > > On Dec 20, 2022, at 8:38 AM, ripe.net at toppas.net wrote: > > > > On the one hand i agree with Stephane, but on the other hand, it is a > fact that there are a few large providers/CDNs who have a significant > share... of specific webservices. I don't like that either, but i can't > deny it either. I agree, that manually selecting those providers/CDNs for > such a measurement could be understood as a statement. But maybe there's > another way, to select which one of those providers/CDNs to measure? > Instead of manually selecting them, there could be some sort of "threshold" > which a provider/CDN has to reach, to be part of this kind of measurement. > This way, it wouldn't be a statement, but a static delimitation. I am > unsure what kind of threshold it could be, and how to detect it. It should > probably be some sort of technical value. > > > > > I’m also thinking of those of us that also have multiple CDN planes, etc.. > and the fact that if we give out a test-point, those customers tend to get > billed for the usage. There’s also a lot of regionality to content and > things, it’s unlikely you would see the same performance in a far-flung > geolocation to a primarily US property or vice-versa. > > Even if you were to do $employer.com that doesn’t mean that content is > hosted on all our servers, they have various functions and roles on our > side, so you end up with all the measurement bias that would occur from > there. I know that things are similar at other CDNs. > > - Jared > -- > ripe-atlas mailing list > ripe-atlas at ripe.net > https://mailman.ripe.net/ > -- Arzhel -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20221222/0c3422f1/attachment.html>
- Previous message (by thread): [atlas] Proposal: Measure well-known CDNs,[CDN-HTTP]
- Next message (by thread): [atlas] Proposal: Measure well-known CDNs,[CDN-HTTP]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]