Re: [Ntp] SNTP, Old crufty software
Miroslav Lichvar <mlichvar@redhat.com> Mon, 15 August 2022 11:22 UTC
Return-Path: <mlichvar@redhat.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 A39BAC1522CA for <ntp@ietfa.amsl.com>; Mon, 15 Aug 2022 04:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.679
X-Spam-Level:
X-Spam-Status: No, score=-2.679 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.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 Q1q_I2jQ934k for <ntp@ietfa.amsl.com>; Mon, 15 Aug 2022 04:22:15 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (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 6BF86C1522BC for <ntp@ietf.org>; Mon, 15 Aug 2022 04:22:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1660562534; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cRTaogfoMjhMmxP3pfk3aAfmI2XrVCkmVDHai8S8WAs=; b=fdzYG6qB3FUe52DUd3zm7DeL8Y6mv6ggpDnFqyKeETlDBSlsB14LiPQyGk+WK/+Jl0Yiwf 9Zto081DvT3Ifx3JJvD2b1QN3YnxpD63qaiQUwAV6GcG8QsjdYZmvplRZISnfFzNmuUYPE HyK3FLH1j7zHx/xfULLlGdeDZ8sXMqQ=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-116-4MLEiNW-O9urmaRstWrt0w-1; Mon, 15 Aug 2022 07:22:13 -0400
X-MC-Unique: 4MLEiNW-O9urmaRstWrt0w-1
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id EAF3B185A79C; Mon, 15 Aug 2022 11:22:12 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7ADFA4050067; Mon, 15 Aug 2022 11:22:12 +0000 (UTC)
Date: Mon, 15 Aug 2022 13:22:11 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <halmurray@sonic.net>
Cc: ntp@ietf.org
Message-ID: <YvosYwavhUmbPoOa@localhost>
References: <20220811222515.06CF528C1CA@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
MIME-Version: 1.0
In-Reply-To: <20220811222515.06CF528C1CA@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/387I_3DsLOTXWAbcOaFr4yqHT-Y>
Subject: Re: [Ntp] SNTP, Old crufty software
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: Mon, 15 Aug 2022 11:22:17 -0000
On Thu, Aug 11, 2022 at 03:25:14PM -0700, Hal Murray wrote: > Has anybody looked at RFC 4330 (SNTP) lately? It's 27 pages. Much of it is > not useful if you are only intereted in the S part of SNTP. It's a lot less > simple than it could be. RFC 4330 was obsoleted by RFC 5905, which has just a single section about SNTP. In the context of NTPv5, where the protocol specification won't describe the usual algorithms, there is just the offset calculation that could be simplified. A separate document describing a simple NTPv5 client might work better. -- Miroslav Lichvar
- [Ntp] SNTP, Old crufty software Hal Murray
- Re: [Ntp] SNTP, Old crufty software Martin Burnicki
- [Ntp] Antw: [EXT] Re: SNTP, Old crufty software Ulrich Windl
- Re: [Ntp] SNTP, Old crufty software James
- Re: [Ntp] SNTP, Old crufty software James Browning
- Re: [Ntp] SNTP, Old crufty software Doug Arnold
- Re: [Ntp] SNTP, Old crufty software Harlan Stenn
- Re: [Ntp] SNTP, Old crufty software Hal Murray
- Re: [Ntp] SNTP, Old crufty software Miroslav Lichvar
- [Ntp] Antw: [EXT] Re: SNTP, Old crufty software Ulrich Windl
- Re: [Ntp] SNTP, Old crufty software Greg.Dowd
- Re: [Ntp] SNTP, Old crufty software Harlan Stenn
- Re: [Ntp] SNTP, Old crufty software Greg.Dowd
- Re: [Ntp] SNTP, Old crufty software Martin Burnicki
- Re: [Ntp] SNTP, Old crufty software Martin Burnicki
- Re: [Ntp] SNTP, Old crufty software Harlan Stenn