attachment
<div dir="ltr"><div>Hi,</div><div><br></div><div>FYI - Roughtime is intended specifically to give "good enough" time for certificate validation</div><div>(+/- 10 seconds) and provide a bootstrap when systems do a full restart - both useful for IPP.</div><div><br></div><div>Note that it's intentionally registered as an "Experimental" protocol (although it's already</div><div>widely deployed in Cloud and CDN infrastructures). </div><div><br></div><div>Cheers,</div><div>- Ira</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">The IESG</b> <span dir="auto"><<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></span><br>Date: Tue, Mar 17, 2026 at 11:33 PM<br>Subject: [Ntp] Document Action: 'Roughtime' to Experimental RFC (draft-ietf-ntp-roughtime-19.txt)<br>To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>Cc: The IESG <<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>>, <<a href="mailto:draft-ietf-ntp-roughtime@ietf.org">draft-ietf-ntp-roughtime@ietf.org</a>>, <<a href="mailto:ek.ietf@gmail.com">ek.ietf@gmail.com</a>>, <<a href="mailto:kodonog@pobox.com">kodonog@pobox.com</a>>, <<a href="mailto:ntp-chairs@ietf.org">ntp-chairs@ietf.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>The IESG has approved the following document:<br>
- 'Roughtime'<br>
(draft-ietf-ntp-roughtime-19.txt) as Experimental RFC<br>
<br>
This document is the product of the Network Time Protocols Working Group.<br>
<br>
The IESG contact persons are Erik Kline and Éric Vyncke.<br>
<br>
A URL of this Internet-Draft is:<br>
<a href="https://datatracker.ietf.org/doc/draft-ietf-ntp-roughtime/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-ntp-roughtime/</a><br>
<br>
<br>
<br>
<br>
Technical Summary<br>
<br>
This document describes Roughtime—a protocol that aims to achieve two<br>
things: secure rough time synchronization even for clients without<br>
any idea of what time it is, and giving clients a format by which to<br>
report any inconsistencies they observe between time servers. This<br>
document specifies the on-wire protocol required for these goals, and<br>
discusses aspects of the ecosystem needed for it to work.<br>
<br>
Working Group Summary<br>
<br>
Was there anything in the WG process that is worth noting?<br>
For example, was there controversy about particular points <br>
or were there decisions where the consensus was<br>
particularly rough? <br>
<br>
Nothing of note.<br>
<br>
Document Quality<br>
<br>
Are there existing implementations of the protocol? Have a <br>
significant number of vendors indicated their plan to<br>
implement the specification? Are there any reviewers that<br>
merit special mention as having done a thorough review,<br>
e.g., one that resulted in important changes or a<br>
conclusion that the document had no substantive issues? If<br>
there was a MIB Doctor, Media Type, or other Expert Review,<br>
what was its course (briefly)? In the case of a Media Type<br>
Review, on what date was the request posted?<br>
<br>
Several existing implementations.<br>
<br>
Personnel<br>
<br>
The Document Shepherd for this document is Karen O'Donoghue. The<br>
Responsible Area Director is Erik Kline.<br>
<br>
IANA Note<br>
<br>
Two new registries, two mime types, one port requested.<br>
<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>