[Ntp] Is it time for a BCP on getting started?
Hal Murray <hmurray@megapathdsl.net> Fri, 26 February 2021 00:35 UTC
Return-Path: <hmurray@megapathdsl.net>
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 C78793A12F1 for <ntp@ietfa.amsl.com>; Thu, 25 Feb 2021 16:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.144
X-Spam-Level: *
X-Spam-Status: No, score=1.144 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HDRS_LCASE=0.099, HELO_DYNAMIC_IPADDR=1.951, PDS_RDNS_DYNAMIC_FP=0.01, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 TryJCjaly9Bn for <ntp@ietfa.amsl.com>; Thu, 25 Feb 2021 16:35:21 -0800 (PST)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id 26EE93A12E8 for <ntp@ietf.org>; Thu, 25 Feb 2021 16:35:20 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 40B8540605C; Thu, 25 Feb 2021 16:35:17 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: NTP WG <ntp@ietf.org>
cc: Hal Murray <hmurray@megapathdsl.net>
From: Hal Murray <hmurray@megapathdsl.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 25 Feb 2021 16:35:17 -0800
Message-Id: <20210226003517.40B8540605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Y0UEJc3w3b2t5C-mZAMBnNKxcIE>
Subject: [Ntp] Is it time for a BCP on getting started?
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: Fri, 26 Feb 2021 00:35:23 -0000
Here is what started this line of thought: > Once Roughtime matures a bit we may consider integrating a Roughtime client > into byztimed for certificate validation purposes. There was an implied "securely" in there. How many time sources are there? RTC/CMOS/TOY clock File system NTP+NTS Roughtime ... Do we have answers, as in the "P" of BCP, or just a collection of how it works and what it needs? Things a system designer should think about. -- These are my opinions. I hate spam.