[Ntp] RFC 10049 on Roughtime: A Protocol for Rough Time Synchronization

rfc-editor@rfc-editor.org Mon, 05 October 2026 20:28 UTC

Received: by mx.ietf.org (Postfix) id 994574B; Mon, 05 Oct 2026 20:28:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc-editor.org; s=mail; t=1791232123; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=/gq6satm1boGViRJnfo6HHwoe2nM0WzARuarhdasZrA=; b=s9a5oVrY+j2rVf1/DJKj+NqsREIFE0Aew/Zur0xDn0sLHZ5iuu88HBk2reztImGyEFFijY b+1AZ9n31c0fn3MNEMK90qB1tJjxDV4UI2qlZ7bDpEsQsMHa8E1gyuwpDw1x6EAFtc2iXl 0AE2drp2keJghxdow+0FxwJ4ty451BA=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=rfc-editor@rfc-editor.org
Received: from celery-84b97d8d5-bs4z4 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 6667313A398DC; Mon, 5 Oct 2026 13:28:43 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Mon, 05 Oct 2026 20:28:43 -0000
message-id: <179123212330.12.2891439008839176641@rfc-editor.org>
Message-ID-Hash: N6AOB4PQN665WWYS3DQIH2N75FHGCN32
X-Message-ID-Hash: N6AOB4PQN665WWYS3DQIH2N75FHGCN32
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ntp.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, ntp@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Ntp] RFC 10049 on Roughtime: A Protocol for Rough Time Synchronization
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/MVHVgVgz1Zyr0xSmL2om8eCV_2Y>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        RFC 10049

        Title:      Roughtime: A Protocol for Rough Time Synchronization
        Author:     W. Ladd,
                    M. Dansarie
        Status:     Experimental
        Stream:     IETF
        Date:       October 2026
        Mailbox:    watsonbladd@gmail.com,
                    marcus@dansarie.se
        Pages:      28


        I-D Tag:    draft-ietf-ntp-roughtime-19

        URL:        https://www.rfc-editor.org/info/rfc10049

        DOI:        10.17487/RFC10049

This document describes Roughtime, an experimental protocol that aims to achieve 
two things: secure, rough time synchronization (even for clients without any 
idea of what time it is) and a format for clients to report any inconsistencies 
they observe between timeservers. This document specifies the on-wire protocol 
required for these goals and discusses aspects of the ecosystem needed for it to work.

This document is a product of the Network Time Protocols Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team