Skip to main content

A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos
draft-ietf-ntp-chronos-25

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ntp-chronos@ietf.org, dsibold.ietf@gmail.com, ek.ietf@gmail.com, ntp-chairs@ietf.org, ntp@ietf.org, odonoghue@isoc.org, rfc-editor@rfc-editor.org
Subject: Document Action: 'A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos' to Informational RFC (draft-ietf-ntp-chronos-25.txt)

The IESG has approved the following document:
- 'A Secure Selection and Filtering Mechanism for the Network Time
   Protocol with Khronos'
  (draft-ietf-ntp-chronos-25.txt) as Informational RFC

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

The IESG contact persons are Erik Kline and Éric Vyncke.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ntp-chronos/


Ballot Text

Technical Summary

   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.

Working Group Summary

   The document has working groups consensus for publication. One person
   expressed opposition. Others either have added supportive comments or
   have been silent.

Document Quality

   The authors have two PoC implementations: one in Python the other in C.
   In addition one ntpd project has setup a project to implement Khronos
   in the NTPd code base.

Personnel

   The Document Shepherd for this document is Dieter Sibold. The
   Responsible Area Director is Erik Kline.

RFC Editor Note