[Ntp] Document for Synchronization Security Guidelines

kristof.teichel@ptb.de Tue, 10 September 2019 17:29 UTC

Return-Path: <kristof.teichel@ptb.de>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id F29F91201CE for <ntp@ietfa.amsl.com>; Tue, 10 Sep 2019 10:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_OBFU_PDF_ATTACH=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id n28NBD9dy1o4 for <ntp@ietfa.amsl.com>; Tue, 10 Sep 2019 10:29:26 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA9A5120041 for <ntp@ietf.org>; Tue, 10 Sep 2019 10:29:25 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de []) by mx1.bs.ptb.de with ESMTP id x8AHTN2u012140-x8AHTN2w012140 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <ntp@ietf.org>; Tue, 10 Sep 2019 19:29:23 +0200
Received: from lotus.bs.ptb.de (lotus.bs.ptb.de []) by smtp-hub.bs.ptb.de (Postfix) with ESMTPS id DB2808465FF for <ntp@ietf.org>; Tue, 10 Sep 2019 19:29:22 +0200 (CEST)
To: "NTP WG" <ntp@ietf.org>
MIME-Version: 1.0
Message-ID: <OFF68B9433.2C6E73E7-ONC1258471.005F21F5-C1258471.0060124C@ptb.de>
From: kristof.teichel@ptb.de
Date: Tue, 10 Sep 2019 19:30:23 +0200
Content-Type: multipart/mixed; boundary="=_mixed 00601246C1258471_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ocgpsgP-giYObUjt7XMrY_aRjgs>
Subject: [Ntp] Document for Synchronization Security Guidelines
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: Tue, 10 Sep 2019 17:29:29 -0000

Hey all,

as I mentioned at the end of the interrim meeting today, I have (as a 
byproduct of compiling my PhD thesis) some text lying around that deals 
with our experience from the last six years or so in designing secure time 
synchronization - for both two-way and one-way communication.
It lists the goals for secure synchronization, first by what the 
participants' interests are, then by what objectives that implies for the 
actual messages that are exchanged. 
It then goes on to describe for each two-way and one-way scenarios a (very 
high-level) blueprint for how to solve all these goals at once.

If anyone were interested in reading this long-ish treatise and commenting 
on what aspects of it might be interesting enough for the WG to put them 
into an actual draft and deal with the further processing of that for some 
BCP or otherwise informational document, I would be very grateful.
I can always do editorial passes to make things less long-winded, but I 
will not get to that before November or so.

Best regards,

(Sorry, I currently only have PDF output conveniently available for my 
LaTeX source)