IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: Going forward with NTP ‑ v5, v4 and approach

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Fri, 19 August 2022 09:26 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 B6A1AC1526E3 for <ntp@ietfa.amsl.com>; Fri, 19 Aug 2022 02:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 yerUHyYN1hRQ for <ntp@ietfa.amsl.com>; Fri, 19 Aug 2022 02:26:18 -0700 (PDT)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [194.94.157.147]) (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 3F94AC14CE2D for <ntp@ietf.org>; Fri, 19 Aug 2022 02:26:18 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 376FE6000050 for <ntp@ietf.org>; Fri, 19 Aug 2022 11:26:16 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 1E306600004D for <ntp@ietf.org>; Fri, 19 Aug 2022 11:26:16 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Fri, 19 Aug 2022 11:26:16 +0200
Message-Id: <62FF5735020000A10004C84F@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.1
Date: Fri, 19 Aug 2022 11:26:13 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: doug.arnold=40meinberg-usa.com@dmarc.ietf.org, kristof.teichel=40ptb.de@dmarc.ietf.org, "ntp@ietf.org" <ntp@ietf.org>
References: <OFBAE2F5D9.2E42DB42-ONC12588A2.00362BE6-C12588A2.003D5155@ptb.de> <AM7PR02MB5765AA103A3A6913C4806765CF6D9@AM7PR02MB5765.eurprd02.prod.outlook.com>
In-Reply-To: <AM7PR02MB5765AA103A3A6913C4806765CF6D9@AM7PR02MB5765.eurprd02.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/2E_5eVlffpOOUoStEN0SwBIbDhc>
Subject: [Ntp] Antw: [EXT] Re: 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: Fri, 19 Aug 2022 09:26:22 -0000

>>> Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org> schrieb am
18.08.2022 um 21:38 in Nachricht
<AM7PR02MB5765AA103A3A6913C4806765CF6D9@AM7PR02MB5765.eurprd02.prod.outlook.com>

> Excellent question.
> 
> 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
> 
> What do others think?

I think steps 1 to 4 forms a loop that is done when no more changes are needed ;-)

Regards,
Ulrich

v2.23.0 | Report a Bug | By Email