[atlas] Anchors as target hosts for SLA

Hi,

On Tue, Jun 06, 2017 at 06:48:33PM +0200, Antonio Prado wrote:
> This Internet transit should meet the following criteria:
> 
> average round trip delay (echo request, echo reply) toward
> $NEAREST_ATLAS_ANCHOR should be less than 100ms on a 10k packets stream
> of pings; packet loss equal or less than 0.02%
> 
> pros, cons, recommendations?

Too simple.  What if that anchor is down, or the anchor host network has
a network bottleneck towards the transit provider you are using?

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.

With the large amount of anchors nowadays, just using the anchor matrix
is actually quite similar to what TTM had, just better... :-)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- 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/20170606/906cbf75/attachment.sig>