IETF Logo Mail Archive

Re: [Ntp] An NTPv5 design sketch

"Salz, Rich" <rsalz@akamai.com> Tue, 21 April 2020 13:35 UTC

Return-Path: <rsalz@akamai.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 E3B643A0C5A for <ntp@ietfa.amsl.com>; Tue, 21 Apr 2020 06:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=akamai.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 wC4c8BKQadRY for <ntp@ietfa.amsl.com>; Tue, 21 Apr 2020 06:35:04 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 897DF3A0C5E for <ntp@ietf.org>; Tue, 21 Apr 2020 06:35:04 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 03LDRTsr001419; Tue, 21 Apr 2020 14:35:03 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=4BAxZ/PsR3W635UUOJ2WNHGi74nI31G+eg7X9aBzeRE=; b=bL6dkfWhruXbbQODHVsLBGqnKpKMqEcT6m7IL1qKUaeMKjLh7zyPvzYfR12Z6Hm/tkBh YienL9peofg/dofgGimzk3ZWlPEOaBFY/2+KpibBetw7QZL5MBbZj4oj2RaztTGAQl8z svLABtgkzJirD3Pf2jgkgZwWXXPj5yK+xk2Tep0VIwWaqLfAg4CDH8zbYb/8Laz5yTeA VgbbUMKzBRxqcgD3UwiezOZAj1hVo7LnFOSPRtQh+964xXQvjJecpLgX1UIgMHWChXVc O40xmokrtA1i6z/kHRvdragUkSK4V7KzeEeUqG2FTVTJdJgrjNtCaEvNaD6uVmZfqW3Q bg==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 30fskjky6f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Apr 2020 14:35:03 +0100
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 03LDW4qM009060; Tue, 21 Apr 2020 09:35:02 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.112]) by prod-mail-ppoint6.akamai.com with ESMTP id 30fvvuaapw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 21 Apr 2020 09:35:01 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.165.123) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 21 Apr 2020 08:34:49 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.006; Tue, 21 Apr 2020 08:34:47 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Miroslav Lichvar <mlichvar@redhat.com>, Daniel Franke <dfoxfranke@gmail.com>
CC: NTP WG <ntp@ietf.org>
Thread-Topic: [Ntp] An NTPv5 design sketch
Thread-Index: AQHWEOYuYEJ8CUQI9kK76gIQM1PTa6h40OGAgAA8gQCAAA4YgIAACmqAgAD4yICAAJCNgIABFBqAgAfu8oA=
Date: Tue, 21 Apr 2020 13:34:46 +0000
Message-ID: <1ECC0FB5-3079-471E-847D-6E8DFBE1B9D7@akamai.com>
References: <CAJm83bBV+Pox3r6KU49ShwMOvr=R+U_vDKJtSZhfT6XX4qWmbA@mail.gmail.com> <20200414112541.GD1945@localhost> <CAJm83bCxuS_X68-pvpOWCPSmjAjTeYNJVuuOEhV-i82R7B28Mg@mail.gmail.com> <20200414155241.GF1945@localhost> <CAJm83bC1EhwQQ=+B7XPbEkvhOWvxU8zjCd290Fj5N43aMJQTkg@mail.gmail.com> <20200415072023.GG1945@localhost> <CAJm83bAEDuLk6vSa82D3smXO4x7iDywoy+FpC=gdm=m3SLrVLg@mail.gmail.com> <20200416082557.GI1945@localhost>
In-Reply-To: <20200416082557.GI1945@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.36.20041300
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.110]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EF47370C63A85D4AA5608773EBD63BA0@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-21_05:2020-04-20, 2020-04-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=771 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2004210108
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-21_05:2020-04-20, 2020-04-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 bulkscore=0 lowpriorityscore=0 impostorscore=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 mlxlogscore=775 adultscore=0 mlxscore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004210107
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/8bTx5aJLFyEMTwYmzzTwNjgM-iI>
Subject: Re: [Ntp] An NTPv5 design sketch
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, 21 Apr 2020 13:35:09 -0000

>    The device may be very simple. It may not have an OS and NTP may be
    the only networking it does. It could be measuring intervals in a
    physics experiment, or controlling a robot in a factory.

I would like to see this use-case *not* be a requirement for NTPv5.  Let's wait for IoT security to settle itself and then adapt to that.
See, for example, https://datatracker.ietf.org/wg/lake/about/

v2.23.0 | Report a Bug | By Email