Re: [Ntp] Antw: Re: Updates to draft-stenn-ntp-extension-fields

Harlan Stenn <stenn@nwtime.org> Mon, 11 December 2017 20:22 UTC

Return-Path: <stenn@nwtime.org>
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 E32891274A5 for <ntp@ietfa.amsl.com>; Mon, 11 Dec 2017 12:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 oUwHNFR-52TW for <ntp@ietfa.amsl.com>; Mon, 11 Dec 2017 12:22:06 -0800 (PST)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 266761273B1 for <ntp@ietf.org>; Mon, 11 Dec 2017 12:22:06 -0800 (PST)
Received: from hms-mbp11.pfcs.com (96-41-166-181.dhcp.mdfd.or.charter.com [96.41.166.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 5AE4FB837; Mon, 11 Dec 2017 20:22:05 +0000 (UTC)
To: Martin Burnicki <martin.burnicki@meinberg.de>, ntp@ietf.org
References: <b7e90464-df9e-7461-5364-cf73ed4d9572@nwtime.org> <20171002133817.GA30411@localhost> <dde31cc4-6e24-d4b6-d9ba-c17b32305786@nwtime.org> <59E4603E020000A1000285FC@gwsmtp1.uni-regensburg.de> <ce8e41f6-9db5-9660-396e-8280b40d563c@nwtime.org> <d385b51a-d217-b4f5-5627-78877a388e1a@meinberg.de>
From: Harlan Stenn <stenn@nwtime.org>
Message-ID: <7f260d89-9d95-37d1-27da-15583ffc5f76@nwtime.org>
Date: Mon, 11 Dec 2017 12:22:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <d385b51a-d217-b4f5-5627-78877a388e1a@meinberg.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/_PJ_JY9cZvLtyQCiJR7UZYbbGxA>
Subject: Re: [Ntp] Antw: Re: Updates to draft-stenn-ntp-extension-fields
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 11 Dec 2017 20:22:08 -0000


On 12/11/17 5:31 AM, Martin Burnicki wrote:
> Folks,
> 
> sorry for jumping in so late.
> 
> I just read RFC-7822
> https://tools.ietf.org/html/rfc7822
> 
> as well as Harlan's proposal for a replacement of that RFC
> https://github.com/hstenn/ietf-ntp-extension-field.git
> 
> IMO Harlan's proposal is very detailed and profound, and provides the
> reader with quite a bit of information about potential pitfalls in
> implementations.
> 
> It also sounds like it's backward compatible with existing NTP
> implementations, which is very important, and on the other hand pretty
> flexible.
> 
> Harlan,
> 
> is there an implementation of this proposal which has been or can be
> tested in real operation?

Thanks for the feedback, Martin!

Yes, I've been running an implementation of this for several/many
months' time.  This code will likely be published in January.

-- 
Harlan Stenn <stenn@nwtime.org>
http://networktimefoundation.org - be a member!