From: corey@lod.com (Corey Lindsly)
Subject: [TUHS] Ping times (was: Code bloat)
Date: Thu, 9 Feb 2017 20:15:26 -0800 (PST) [thread overview]
Message-ID: <20170210041526.D3C1140B9@lod.com> (raw)
In-Reply-To: <2993F3BB-9286-4523-A7D6-FDFE57A6D2BD@superglobalmegacorp.com>
> 8.8.8.8 is a multicast. Google has these servers all over the world so
> it's no surprise that everyone has good timing to them....
Well, technically it's anycast, which is conceptually similar to
multicast but a distinct routing protocol. Anycast is one-to-nearest while
multicast is one-to-many (selected).
--corey
next prev parent reply other threads:[~2017-02-10 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.220.1486670111.3779.tuhs@minnie.tuhs.org>
2017-02-09 21:13 ` Johnny Billquist
2017-02-09 23:03 ` Joerg Schilling
2017-02-09 23:09 ` [TUHS] Ping times Johnny Billquist
2017-02-10 2:07 ` [TUHS] Ping times (was: Code bloat) Jason Stevens
2017-02-10 4:15 ` Corey Lindsly [this message]
2017-02-10 8:05 ` [TUHS] Ping times Johnny Billquist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170210041526.D3C1140B9@lod.com \
--to=corey@lod.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).