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/ripe-atlas@ripe.net/
[atlas] Anchors as target hosts for SLA
- Previous message (by thread): [atlas] Anchors as target hosts for SLA
- Next message (by thread): [atlas] Anchors as target hosts for SLA
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antonio Prado
thinkofit at gmail.com
Tue Jun 6 19:46:42 CEST 2017
On 6/6/17 7:03 PM, Gert Doering wrote: > Too simple. What if that anchor is down, or the anchor host network has > a network bottleneck towards the transit provider you are using? well, I selected two anchors placed in two different NAPs where all ISPs in my scenario are present. so, not a big concern if one anchor is down. the other issue about possible bottlenecks is not applicable in that context. > So you need something that averages over multiple anchors - we used to > do that via TTM ("if our TTM hosts can reach more than 80% of all other > TTM hosts, we declare the Internet to be in good working condition" - note > the "80%", because something is always down somewhere) but haven't come > around to define & implement something based on ATLAS yet. I like the idea and it should definitely be the way to go. thank you -- antonio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/ripe-atlas/attachments/20170606/eeea92d6/attachment.sig>
- Previous message (by thread): [atlas] Anchors as target hosts for SLA
- Next message (by thread): [atlas] Anchors as target hosts for SLA
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]