attachment
<div dir="ltr"><div>Hi,</div><div><br></div><div>Stable and consensus-based with many implementations of a simple clock-setting</div><div>protocol for constrained devices (evolved from the original Google work).</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <span dir="auto"><<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>></span><br>Date: Mon, Oct 5, 2026 at 4:28 PM<br>Subject: [Ntp] RFC 10049 on Roughtime: A Protocol for Rough Time Synchronization<br>To: <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>>, <<a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a>><br>Cc: <<a href="mailto:drafts-update-ref@iana.org">drafts-update-ref@iana.org</a>>, <<a href="mailto:ntp@ietf.org">ntp@ietf.org</a>>, <<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>><br></div><br><br>A new Request for Comments is now available in online RFC libraries.<br>
<br>
RFC 10049<br>
<br>
Title: Roughtime: A Protocol for Rough Time Synchronization<br>
Author: W. Ladd,<br>
M. Dansarie<br>
Status: Experimental<br>
Stream: IETF<br>
Date: October 2026<br>
Mailbox: <a href="mailto:watsonbladd@gmail.com" target="_blank">watsonbladd@gmail.com</a>,<br>
<a href="mailto:marcus@dansarie.se" target="_blank">marcus@dansarie.se</a><br>
Pages: 28<br>
<br>
<br>
I-D Tag: draft-ietf-ntp-roughtime-19<br>
<br>
URL: <a href="https://www.rfc-editor.org/info/rfc10049" rel="noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc10049</a><br>
<br>
DOI: 10.17487/RFC10049<br>
<br>
This document describes Roughtime, an experimental protocol that aims to achieve <br>
two things: secure, rough time synchronization (even for clients without any <br>
idea of what time it is) and a format for clients to report any inconsistencies <br>
they observe between timeservers. This document specifies the on-wire protocol <br>
required for these goals and discusses aspects of the ecosystem needed for it to work.<br>
<br>
This document is a product of the Network Time Protocols Working Group of the IETF.<br>
<br>
EXPERIMENTAL: This memo defines an Experimental Protocol for the<br>
Internet community. It does not specify an Internet standard of any<br>
kind. Discussion and suggestions for improvement are requested.<br>
Distribution of this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer" target="_blank">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search/" rel="noreferrer" target="_blank">https://www.rfc-editor.org/search/</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/series/rfc-download/" rel="noreferrer" target="_blank">https://www.rfc-editor.org/series/rfc-download/</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
_______________________________________________<br>
ntp mailing list -- <a href="mailto:ntp@ietf.org" target="_blank">ntp@ietf.org</a><br>
To unsubscribe send an email to <a href="mailto:ntp-leave@ietf.org" target="_blank">ntp-leave@ietf.org</a><br>
</div></div>