IETF Logo Mail Archive

Re: [Ntp] Going forward with NTP - v5, v4 and approach

"Salz, Rich" <rsalz@akamai.com> Thu, 18 August 2022 20:02 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 D1FC0C1522AF; Thu, 18 Aug 2022 13:02:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level:
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amZfGq1o5bMy; Thu, 18 Aug 2022 13:02:38 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 7A12DC14F74A; Thu, 18 Aug 2022 13:02:38 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 27IItX84014588; Thu, 18 Aug 2022 21:02:37 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=S/uAMijX2W3eKsyDhSS3FRWvUius5T2jM9GlVKUkAtc=; b=NJ2N+AiKn/y3q97sVie0h6Y8MWD4X2mXKr2K39wjwSxT2GcPkeTaP2GbrSi6UC6+0wTu Ndscso2Izd0TOGh/0oNNz66IESG6kXSwlHU3qXCri0EGrFu+AieW/TJBstZ7SbRW1XHw pSc5zbD6gIRlyrYbUwDnOEaZ508kRY4IVZQpkp8Xzzf5lTykVh8cd4/s/vm3GSysplQG anEcPvCObAq+v5k45Zmsjqe+RuFucxdkVXAnoI/0BNLSW0r/uVZvmFscLVTSbMYyJc/r VQK4M68cWa3Hav2moqMfKRmLHAgQlRYs7LTT49gJH65LzoPdonAjYeMQ0T/jMf02RRag JA==
Received: from prod-mail-ppoint4 (a72-247-45-32.deploy.static.akamaitechnologies.com [72.247.45.32] (may be forged)) by mx0b-00190b01.pphosted.com (PPS) with ESMTPS id 3j0yhjry4y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Aug 2022 21:02:37 +0100
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.17.1.5/8.17.1.5) with ESMTP id 27IHJeN9008310; Thu, 18 Aug 2022 16:02:36 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.204]) by prod-mail-ppoint4.akamai.com (PPS) with ESMTPS id 3hx79wv57w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Aug 2022 16:02:36 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb3.msg.corp.akamai.com (172.27.50.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.9; Thu, 18 Aug 2022 13:02:36 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1118.009; Thu, 18 Aug 2022 13:02:36 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org>, "kristof.teichel=40ptb.de@dmarc.ietf.org" <kristof.teichel=40ptb.de@dmarc.ietf.org>, NTP WG <ntp@ietf.org>
Thread-Topic: [Ntp] Going forward with NTP - v5, v4 and approach
Thread-Index: AQHYsvMUPq/7M8s6n0yuipOihyGzbK21g4SA///DyIA=
Date: Thu, 18 Aug 2022 20:02:35 +0000
Message-ID: <D3313BBE-71EF-4BC5-9755-87875A9A7757@akamai.com>
References: <OFBAE2F5D9.2E42DB42-ONC12588A2.00362BE6-C12588A2.003D5155@ptb.de> <AM7PR02MB5765AA103A3A6913C4806765CF6D9@AM7PR02MB5765.eurprd02.prod.outlook.com>
In-Reply-To: <AM7PR02MB5765AA103A3A6913C4806765CF6D9@AM7PR02MB5765.eurprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.64.22081401
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_D3313BBE71EF4BC5975587875A9A7757akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-08-18_14,2022-08-18_01,2022-06-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 malwarescore=0 adultscore=0 suspectscore=0 spamscore=0 phishscore=0 mlxscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2207270000 definitions=main-2208180073
X-Proofpoint-GUID: 3cUte_VnHI30EacA5yFvxMrciAvJ1jYV
X-Proofpoint-ORIG-GUID: 3cUte_VnHI30EacA5yFvxMrciAvJ1jYV
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-08-18_14,2022-08-18_01,2022-06-22_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 adultscore=0 impostorscore=0 mlxscore=0 phishscore=0 spamscore=0 clxscore=1011 bulkscore=0 lowpriorityscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2207270000 definitions=main-2208180073
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/x7lqKc0pR-NcRjQ6r5itBNi08KI>
Subject: Re: [Ntp] Going forward with NTP - v5, v4 and approach
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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, 18 Aug 2022 20:02:42 -0000

>I expect the process to work something like this:

  1.  Somewhat complete draft of ntpv5
  2.  First implementations tested with each other
  3.  Tweak first implementations to work well together
  4.  Refine draft to reflect any changes or clarifications that were needed for interoperability
  5.  Publish

In the QUIC and TLS working groups, there was the expectation that the base draft wasn’t done, and that steps 1-4 would need to be repeated multiple times. I suggest the NTP WG have the same expectation.  Also, think about defining an extension for “which version of the draft” is going out on the wire; that was a great aide to interop, and not having the extension was an indication that it’s the final RFC version.

Also define a test matrix.  Client, server, peer at same strata, peer above or below seems likely.  Look at https://interop.seemann.io/ as an (impressive!) example. And consider working with https://caniuse.com eventually.

v2.23.0 | Report a Bug | By Email