Last Call: <draft-ietf-ntp-chronos-14.txt> (A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 08 June 2023 12:58 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-ntp-chronos-14.txt> (A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-ntp-chronos@ietf.org, dsibold.ietf@gmail.com, ek.ietf@gmail.com, ntp-chairs@ietf.org, ntp@ietf.org, odonoghue@isoc.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <168622908866.33470.11629194371802687734@ietfa.amsl.com>
Date: Thu, 08 Jun 2023 05:58:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kNhFM67BE_HEEyvfZKimq55wRmc>

The IESG has received a request from the Network Time Protocols WG (ntp) to
consider the following document: - 'A Secure Selection and Filtering
Mechanism for the Network Time
   Protocol with Khronos'
  <draft-ietf-ntp-chronos-14.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-06-22. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   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 specifies an extension to the
   NTPv4 client, named Khronos, which is used as a "watchdog" alongside
   NTPv4, and 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 any current or future time protocol.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-ntp-chronos/



No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-ntp-chronos-14.txt> (A Sec… The IESG