-
I recently implemented the draft-ietf-ntp-roughtime-08 and found no major issues, but there are a number of things in the draft that could use clarification:
- [x] Section 5.1.4: Replace reference …
-
Hi,
Considering the protocol would be approved as-is in the IETF draft, and that at least the MIDP format is incompatible with current de-facto roughtime, what would be the update path?
Will the…
-
[Ben] Requiring the signing certificate to be sent in every packet means that some algorithms will not be usable, since their certificates won’t fit, and probably also means it won’t be possible to fi…
-
[Hayden] The I-D mandates the use of Ed25519 due to the signature size and efficiency in computation of the signature. Roughtime server operators may have other requirements on key usage however, an…
-
`roughtime` normally is used in conjunction with an interval intersection algorithm to establish an agreement over current time. Would be nice to embed this functionality in `vroughtime`.
-
Related to #1731
This issue is for discussing the effects of long clock jumps, backward and forward, in a chain using PBTS.
PBTS assumes nodes are synchronized to a source of truth clock using …
-
NTP is installed but obviously cannot work. Needs to be replaced with tlsdate (waiting on debian package).
-
# Feature Request #
## Environment ##
Bare metal
## Desired Feature ##
Ignition runs early in boot, before any time synchronization, and runs on newly-installed systems which may not have …
-
So currently for secure time there are essentially two options:
## NTS (Network Time Security) | [RFC 8915](https://datatracker.ietf.org/doc/html/rfc8915)
* NTS is an actual standard, not just a…
-
There are a growing number of servers that won't talk the pre-IETF version of roughtime. We should add some minimal support to talk to those servers.
@wingel has added support for this on their for…