From: Leo Famulari <leo@famulari.name>
To: 27759@debbugs.gnu.org
Subject: bug#27759: NTP pool vendor zone
Date: Tue, 18 Jul 2017 17:42:56 -0400 [thread overview]
Message-ID: <20170718214256.GA20175@jasmine.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Currently our ntp-service uses the top-level NTP pool servers [0]:
(define %ntp-servers
;; Default set of NTP servers.
'("0.pool.ntp.org"
"1.pool.ntp.org"
"2.pool.ntp.org"))
However, the NTP Pool project requests that operating system vendors
(that's us!) don't use these servers directly [1]:
------
You must get approval from the server operator before you hardcode any
IP addresses or hostnames. This is easy to get if your own organization
runs the NTP servers you are planning to use. In most other cases you
will not get it.
Do not use the standard pool.ntp.org names as a default configuration in
your system. The NTP Pool can offer services for you, but it must be
setup in advance (see below).
------
They recommend we apply for a vendor zone instead [2]. We would not have
to run our own NTP servers.
Does anyone know if GNU or the FSF have a vendor zone we could use?
Otherwise, we should apply for one and adjust our ntp-service.
[0]
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/networking.scm?id=ec5c24f9a8421172a0cf9133d512014b31815a76#n336
[1]
http://www.pool.ntp.org/en/vendors.html#basic-guidelines
[2]
http://www.pool.ntp.org/en/vendors.html#vendor-zone
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-07-18 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:42 Leo Famulari [this message]
2017-07-19 20:40 ` bug#27759: NTP pool vendor zone Ludovic Courtès
2017-07-20 18:59 ` Leo Famulari
2017-07-30 2:43 ` Leo Famulari
2017-07-30 12:36 ` Ludovic Courtès
2017-07-31 0:28 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170718214256.GA20175@jasmine.lan \
--to=leo@famulari.name \
--cc=27759@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).