IETF Logo Mail Archive

Re: [Ntp] Modular NTP

Danny Mayer <mayer@pdmconsulting.net> Sat, 25 April 2020 17:16 UTC

Return-Path: <mayer@pdmconsulting.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 9F9323A0C07 for <ntp@ietfa.amsl.com>; Sat, 25 Apr 2020 10:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 sPhoaNiC4rOX for <ntp@ietfa.amsl.com>; Sat, 25 Apr 2020 10:16:46 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (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 A9F2E3A0BFA for <ntp@ietf.org>; Sat, 25 Apr 2020 10:16:36 -0700 (PDT)
Received: from [10.10.10.122] (pool-71-174-223-234.bstnma.east.verizon.net [71.174.223.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 498d4M00yfzL7d; Sat, 25 Apr 2020 17:16:34 +0000 (UTC)
To: Doug Arnold <doug.arnold@meinberg-usa.com>, NTP WG <ntp@ietf.org>
References: <729A897B-2825-4E41-A844-286BB9500C5D@akamai.com> <DB8PR02MB561107661708391F34D09768CFD00@DB8PR02MB5611.eurprd02.prod.outlook.com>
From: Danny Mayer <mayer@pdmconsulting.net>
X-Pep-Version: 2.0
Message-ID: <af60d454-346b-2e11-119a-5b31c51c39c4@pdmconsulting.net>
Date: Sat, 25 Apr 2020 13:16:33 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <DB8PR02MB561107661708391F34D09768CFD00@DB8PR02MB5611.eurprd02.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------5A2446EDCAD9ED3A9BFFCA73"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/3L21SInRHcDgZFurAtu4F4Th1fs>
Subject: Re: [Ntp] Modular NTP
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: Sat, 25 Apr 2020 17:16:55 -0000

What's missing is the data analysis engine between the protocol engine
and the clock control. Nothing gets to the clock control that does not
get through the analysis engine. This is the core of NTP. Everything
else is just detail.


Danny


On 4/24/20 1:17 PM, Doug Arnold wrote:
> Here is a PDF version.
>
> Doug
>
> ------------------------------------------------------------------------
> *From:* Salz, Rich <rsalz@akamai.com>
> *Sent:* Friday, April 24, 2020 10:08 AM
> *To:* Doug Arnold <doug.arnold@meinberg-usa.com>
> *Subject:* Re: [Ntp] Modular NTP
>  
>
> Maybe post a PDF/export?
>
>  
>
> *From: *"doug.arnold@meinberg-usa.com" <doug.arnold@meinberg-usa.com>
> *Date: *Friday, April 24, 2020 at 12:55 PM
> *To: *NTP WG <ntp@ietf.org>
> *Subject: *[Ntp] Modular NTP
>
>  
>
> Perhaps the idea of a modular NTP will be more clear with a diagram of
> how it might work.
>
>  
>
> Doug
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp

v2.23.0 | Report a Bug | By Email