Re: [Ntp] Calls for Adoption -- NTP Extension Field drafts -- Four separate drafts
kristof.teichel@ptb.de Fri, 30 August 2019 12:33 UTC
Return-Path: <kristof.teichel@ptb.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 B9E96120841 for <ntp@ietfa.amsl.com>; Fri, 30 Aug 2019 05:33:57 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=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 wZ7tprtI4AqV for <ntp@ietfa.amsl.com>; Fri, 30 Aug 2019 05:33:55 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [192.53.103.120]) (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 A9743120086 for <ntp@ietf.org>; Fri, 30 Aug 2019 05:33:54 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de with ESMTP id x7UCXrO2020947-x7UCXrO4020947 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <ntp@ietf.org>; Fri, 30 Aug 2019 14:33:53 +0200
Received: from lotus.bs.ptb.de (lotus.bs.ptb.de [141.25.85.200]) by smtp-hub.bs.ptb.de (Postfix) with ESMTPS id 0782F83A8A3 for <ntp@ietf.org>; Fri, 30 Aug 2019 14:33:52 +0200 (CEST)
In-Reply-To: <BCA949D7-7D92-43A9-9766-573559A9FC70@meinberg.de>
References: <1B4A56E7-16A6-4767-9268-BCF4BEB9A247@isoc.org> <BCA949D7-7D92-43A9-9766-573559A9FC70@meinberg.de>
To: NTP WG <ntp@ietf.org>
MIME-Version: 1.0
Message-ID: <OFC6231084.08441372-ONC1258466.00437972-C1258466.0045045E@ptb.de>
From: kristof.teichel@ptb.de
Date: Fri, 30 Aug 2019 14:34:43 +0200
Content-Type: multipart/alternative; boundary="=_alternative 0045045BC1258466_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/xRJZMEaiU6q_-XjM9CLLKgh45oo>
Subject: Re: [Ntp] Calls for Adoption -- NTP Extension Field drafts -- Four separate drafts
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: Fri, 30 Aug 2019 12:33:58 -0000
Hello all, I also oppose adoption of the four draft as documents intended for use with NTPv4. I broadly agree with Heiko's assessment insofar as I think most of the individual content in the four drafts is relevant, but should be treated in a different context: not as an attempt to repair the holes that are opening up in NTPv4, but as a set of principles going into the next revision of NTP ("NTPv5", likely). Best regards, Kristof P.S.: This is especially drastic for the I-DO proposal, where I do not see how it makes sense to try to catch implementation that are too old to understand certain newer EFs by forcing them to understand another new EF with which they can talk about which EFs they do understand. It does seem important to do something akin to this, but I really think it only makes sense if you can assume ALL implementations to a) understand the I-DO-inspired EF and b) be able to use crypto methods to provide authentication for whatever is in the I-DO-inspired EF. Semi-related, I really believe NTPv5 should enable behavior that splits messages (especially server responses) into two parts, the first as small as possible, basically only an identifier saying that it is an NTP packet and providing an ID for the association/exchange it belongs to, the second carrying all the timestamps and meta information. This would enable an almost completely free choice of information that a client could request, each piece of it in its own extension field, without it endangering speed or accuracy. But it is another feature you can only have if you can expect all participants to understand it. Von: "Heiko Gerstung" <heiko.gerstung@meinberg.de> An: "Karen O'Donoghue" <odonoghue@isoc.org>, "ntp@ietf.org" <ntp@ietf.org> Datum: 28.08.2019 08:55 Betreff: Re: [Ntp] Calls for Adoption -- NTP Extension Field drafts -- Four separate drafts Gesendet von: "ntp" <ntp-bounces@ietf.org> Hi, I do not support adopting all four drafts, I believe that we should either integrate them into a new revision of NTP ("NTPv5") or fix them problems/issues they address in that new "NTPv5" RFC. Most of the issues addressed by those drafts can be easily solved by changing/expanding the NTP packet format for "NTPv5". The "REFID" draft would be obsolete if an NTPv5 packet header for a server mode packet by definition includes a "MY_ID" field. The "MAC/last extension field" draft would be obsolete if we define that NTPv5 does only support Extension Fields as allowed additional data and a MAC in v5 is always transported inside an extension field (the "MAC-EF" approach as described in the draft, for example). The "I-DO extension field" draft would be something I would integrate into a "NTPv5" RFC as a mandatory requirement for NTP servers. The "Extended Information Extension Field" draft would be obsolete if we introduce either additional packet header fields in v5 or just defined a new EF for information that we think should be available from the server. That EF could be sent or not, based on whether the client wants it or not (indicated by an EF sent by that client in its request, for example). Best Regards, Heiko -- Heiko Gerstung Managing Director MEINBERG® Funkuhren GmbH & Co. KG Lange Wand 9 D-31812 Bad Pyrmont, Germany Phone: +49 (0)5281 9309-404 Fax: +49 (0)5281 9309-9404 Amtsgericht Hannover 17HRA 100322 Geschäftsführer/Management: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Email: heiko.gerstung@meinberg.de Web: Deutsch https://www.meinberg.de English https://www.meinbergglobal.com Do not miss our Time Synchronization Blog: https://blog.meinbergglobal.com Connect via LinkedIn: https://www.linkedin.com/in/heikogerstung On 28.08.19, 05:38 "ntp im Auftrag von Karen O'Donoghue" <ntp-bounces@ietf.org im Auftrag von odonoghue@isoc.org> wrote: Folks, The following four drafts are four different proposals for new extension fields. Please review each draft and indicate whether these should be adopted by the working group. I am sending them all as one set because they are all extension fields, but we need a response for each draft listed below. Thanks! Karen and Dieter 1. Network Time Protocol Extended Information Extension Field https://datatracker.ietf.org/doc/draft-stenn-ntp-extended-information/ 2. Network Time Protocol I-Do Extension Field https://datatracker.ietf.org/doc/draft-stenn-ntp-i-do/ 3. Network Time Protocol MAC/Last Extension Fields https://datatracker.ietf.org/doc/draft-stenn-ntp-mac-last-ef/ 4. Network Time Protocol Suggested REFID Extension Field https://datatracker.ietf.org/doc/draft-stenn-ntp-suggest-refid/ _______________________________________________ ntp mailing list ntp@ietf.org https://www.ietf.org/mailman/listinfo/ntp _______________________________________________ ntp mailing list ntp@ietf.org https://www.ietf.org/mailman/listinfo/ntp
- [Ntp] Calls for Adoption -- NTP Extension Field d… Karen O'Donoghue
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Heiko Gerstung
- [Ntp] Antw: Re: Calls for Adoption -- NTP Extensi… Ulrich Windl
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… tglassey@earthlink.net
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- N… Ulrich Windl
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Daniel Franke
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Heiko Gerstung
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Watson Ladd
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Salz, Rich
- [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- N… Ulrich Windl
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Dieter Sibold
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… kristof.teichel
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Magnus Danielson
- [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- N… Ulrich Windl
- [Ntp] Antw: Antw: Re: Antw: Re: Calls for Adoptio… Ulrich Windl
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Heiko Gerstung
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Hal Murray
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Miroslav Lichvar
- [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- N… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Harlan Stenn
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Magnus Danielson
- Re: [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Daniel Franke
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Hal Murray
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Harlan Stenn
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Heiko Gerstung
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Hal Murray
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Miroslav Lichvar
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Heiko Gerstung
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for… Watson Ladd
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Salz, Rich
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Daniel Franke
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Salz, Rich
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Daniel Franke
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Salz, Rich
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Salz, Rich
- [Ntp] NTP errors Hal Murray
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Harlan Stenn
- [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- N… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Watson Ladd
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Hal Murray
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Hal Murray
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- Re: [Ntp] Calls for Adoption -- NTP Extension Fie… Fernando Gont
- Re: [Ntp] Antw: Re: Calls for Adoption -- NTP Ext… Miroslav Lichvar
- [Ntp] Antw: Re: Antw: Re: Calls for Adoption -- N… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Harlan Stenn
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Miroslav Lichvar
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for… Watson Ladd
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Hal Murray
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Mark Atwood
- Re: [Ntp] Antw: Re: Antw: Re: Calls for Adoption … Steven Sommars
- [Ntp] Antw: Re: Antw: Re: Antw: Re: Calls for Ado… Ulrich Windl