[Ntp] RFC 9523 on A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos
rfc-editor@rfc-editor.org Wed, 21 February 2024 23:28 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9CA3C151527; Wed, 21 Feb 2024 15:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NE8Zno5ak4r; Wed, 21 Feb 2024 15:28:44 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E640C14F6B1; Wed, 21 Feb 2024 15:28:44 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 101B11F3B440; Wed, 21 Feb 2024 15:28:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ntp@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240221232844.101B11F3B440@rfcpa.amsl.com>
Date: Wed, 21 Feb 2024 15:28:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ZsGhvYY0isz2jPbpWyb_9fjV4GQ>
Subject: [Ntp] RFC 9523 on A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2024 23:28:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9523
Title: A Secure Selection and Filtering Mechanism
for the Network Time Protocol with Khronos
Author: N. Rozen-Schiff,
D. Dolev,
T. Mizrahi,
M. Schapira
Status: Informational
Stream: IETF
Date: February 2024
Mailbox: neta.r.schiff@gmail.com,
danny.dolev@mail.huji.ac.il,
tal.mizrahi.phd@gmail.com,
schapiram@huji.ac.il
Pages: 13
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ntp-chronos-25.txt
URL: https://www.rfc-editor.org/info/rfc9523
DOI: 10.17487/RFC9523
The Network Time Protocol version 4 (NTPv4), as defined in RFC 5905,
is the mechanism used by NTP clients to synchronize with NTP servers
across the Internet. This document describes a companion application
to the NTPv4 client, named "Khronos", that is used as a "watchdog"
alongside NTPv4 and that provides improved security against
time-shifting attacks. Khronos involves changes to the NTP client's
system process only. Since it does not affect the wire protocol, the
Khronos mechanism is applicable to current and future time protocols.
This document is a product of the Network Time Protocols Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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/retrieve/bulk
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
Association Management Solutions, LLC