From: "Ron Frazier (NTP)" <timekeepingntplist@c3energy.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] ntp manycast?
Date: Sun, 25 Mar 2012 16:19:22 -0400 [thread overview]
Message-ID: <4F6F7DCA.8060302@c3energy.com> (raw)
In-Reply-To: <CAA93jw5qeBtdy9f1Gs6ups9Sr=pB09JJSnOq1s2i3G7cKzb22Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
I've never tried it. I don't think there are that many people on this
particular list. You could try posting this on the NTP questions list.
I'll bet you get some response.
http://lists.ntp.org/listinfo/questions
Sincerely,
Ron
On 3/25/2012 3:25 PM, Dave Taht wrote:
>
>
> On Fri, Mar 23, 2012 at 11:45 PM, Dave Taht <dave.taht@gmail.com
> <mailto:dave.taht@gmail.com>> wrote:
>
> I'm curious if anyone out there has actually set up a ntp 'manycast'
> server/clients to get authenticated time?
>
> Similarly autokey...
>
> Am interested in:
>
> A) HOW? The website is not very clear....
> B) Overhead
> D) Latency
>
> The idea of secure, broadcast time over a mesh seems reassuring, as is
> the idea of connecting to each others (not central servers) gps fed
> ntp clocks....
>
>
> the silence is deafening...
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608 <tel:1-239-829-5608>
> http://www.bufferbloat.net
>
>
--
(PS - If you email me and don't get a quick response, don't be concerned.
I get about 300 emails per day from alternate energy mailing lists and
such. I don't always see new messages very quickly. If you need a
reply and have not heard from me in 1 - 2 weeks, send your message again.)
Ron Frazier
timekeepingdude AT c3energy.com
[-- Attachment #2: Type: text/html, Size: 2525 bytes --]
prev parent reply other threads:[~2012-03-25 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 6:45 Dave Taht
2012-03-25 19:25 ` Dave Taht
2012-03-25 20:19 ` Ron Frazier (NTP) [this message]
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=4F6F7DCA.8060302@c3energy.com \
--to=timekeepingntplist@c3energy.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/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