[Ntp] Latest Version of Chronos

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Thu, 06 August 2020 06:53 UTC

Return-Path: <tal.mizrahi.phd@gmail.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 98CD33A0F4A for <ntp@ietfa.amsl.com>; Wed, 5 Aug 2020 23:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZKTX8vZXAlc for <ntp@ietfa.amsl.com>; Wed, 5 Aug 2020 23:53:32 -0700 (PDT)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 111083A0D74 for <ntp@ietf.org>; Wed, 5 Aug 2020 23:53:32 -0700 (PDT)
Received: by mail-wm1-x32f.google.com with SMTP id d190so7829608wmd.4 for <ntp@ietf.org>; Wed, 05 Aug 2020 23:53:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=iAwGC+bZ5W+MpswR+I0xYr5+6fQT8rxtZr8gewy1Nnk=; b=M6ERi0ToF0B4aqGXCPJzosH6rPGNOzXaCX/x8fVgk//DqtvQTQrXUE47fhACLFVaWY pyL/BDUGVf13k1JxBS0zerjP3hSD6QRD/srEHDB6DYOExvSQ2zHMCtNLRrDCYZgiUP/6 FX0MPhgsJ4rMIPqQwpV601w/QVJu4MYpRFpQdq9+/XtWsHeVF7340XLDmGe6r01ZuiEw wrzm0a3QEgbzob701GgNWOf1nCNSmgFceuCmaBQROuv6pDE1rkxatwEUc/8naeKOL30B vtEYemUHyV5bfj/fhvqkbFbYPYYwAP9TN/zeWFCFZhsDCyoR1k2V19K06q885gqNkdlh S7Cw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=iAwGC+bZ5W+MpswR+I0xYr5+6fQT8rxtZr8gewy1Nnk=; b=WToO43uvPznLi2jHxVZ6Z3kB+pzl26CxQGsFxb0t53zRzKDSFqWFVhc+kWyk9sV4Ya QV+LM9Z2hYlT3v78SMHmj2FaWyZ1KbV0aY8/xgJMBtw/Xuf/B3CoAb4DHBDo6QEXLXvM ZaF3odCpAPnUuJkKGr0y0/vYAaNOWBVhIGJiBDiszvxO1RZV8AA2PY2/teuEiPIqTvuu YgcsqYjPNza2XwduhQmLwccyXojrZSYryhIxLOG/Ju2on3uqNr9uDgAMr8Z0mbIfMYW9 yTyfiHhkX7ckXzjYWh0GWN45wg9awb+L/aqssFMs8gWnHNB0gihgXyg74ElJTYyCTGnA UIAA==
X-Gm-Message-State: AOAM531uHAl9+rsMm2NN30vMLDA6uFhh6i+0MgbupI7Gg3T9o1E+zDpK BcW1XZvU5lkAd3CQIO5av1S9R5IO8INNypxCxJcLI43U2JAX7g==
X-Google-Smtp-Source: ABdhPJyPesmr+8BjnXvnA3qk6mE4RGnKd1647hwc7llJBbwCk+QGnU2r2iJW9T1OCcErn3kcaGO8sY6j8zVop2/3rCs=
X-Received: by 2002:a1c:7fd3:: with SMTP id a202mr6344625wmd.67.1596696810248; Wed, 05 Aug 2020 23:53:30 -0700 (PDT)
MIME-Version: 1.0
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Thu, 06 Aug 2020 09:53:18 +0300
Message-ID: <CABUE3XkU6XcdwYuBVy=qy_Q=U44-wn2djYAbv=jNAaQOm2XS+w@mail.gmail.com>
To: NTP WG <ntp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/6Ra8tpM2JDsEedb_CI7RQvLlUGs>
Subject: [Ntp] Latest Version of Chronos
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Thu, 06 Aug 2020 06:53:34 -0000

Hi,

Last week we presented the latest updates to the Chronos draft.

In a nutshell, Chronos is now defined as a watchdog, which
periodically monitors the NTP clock and only when a suspected attack
is detected does the Chronos algorithm take over, replacing the NTP
selection and combining algorithm.

We believe this approach resolves the concerns that were raised about
the potentially low precision of previous versions of Chronos.

We would highly appreciate feedback about the current version of Chronos.

Best regards,
On behalf of the Chronos authors.


A link to the presentation:
https://www.ietf.org/proceedings/108/slides/slides-108-ntp-a-secure-selection-and-filtering-mechanism-for-the-network-time-protocol-version-4-00

A link to the latest draft:
https://tools.ietf.org/html/draft-ietf-ntp-chronos-00