[Ntp] Antwort: Re: The bump, or why NTP v5 must specify impulse response
kristof.teichel@ptb.de Fri, 17 April 2020 10:21 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 8449B3A0794 for <ntp@ietfa.amsl.com>; Fri, 17 Apr 2020 03:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.42
X-Spam-Level:
X-Spam-Status: No, score=-1.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, HTML_NONELEMENT_30_40=0.001, MIME_HTML_ONLY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 BRgs1JIkwhMh for <ntp@ietfa.amsl.com>; Fri, 17 Apr 2020 03:21:02 -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 C457B3A078F for <ntp@ietf.org>; Fri, 17 Apr 2020 03:21:00 -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 03HAKw1B023398-03HAKw1D023398 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <ntp@ietf.org>; Fri, 17 Apr 2020 12:20:58 +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 DBA2C94111F for <ntp@ietf.org>; Fri, 17 Apr 2020 12:20:58 +0200 (CEST)
MIME-Version: 1.0
X-Disclaimed: 1
Sensitivity:
Importance: Normal
X-Priority: 3 (Normal)
In-Reply-To: <E591F38A-A303-4077-BC4C-A61AB7867F83@gmail.com>
References: <E591F38A-A303-4077-BC4C-A61AB7867F83@gmail.com>, <CACsn0c=zzDKP6iBjPJWGF0rkqSaY3AY738ynGwDZO14sdBJ-Bg@mail.gmail.com> <CAJm83bB2A3VUxXX47Y0ubmS9Xne7PRSyV_xHY_D9YvHjqE-vFA@mail.gmail.com> <CACsn0cm3jpKZTUQ=novTgVaFhc1xCJgmUF3oOgdrzQa-HgOCUQ@mail.gmail.com> <CAJm83bAqbMMs2W3SyH+3c17wcC85paY4-_jk2SxczgsxBLyYyA@mail.gmail.com> <CAJm83bAQeR_6U3jgmbWzdus3pu+OO2_KP+M9RtbCFYOfDQy4dw@mail.gmail.com> <DB8PR02MB56111CCA23CDCF97A3C9F3E8CFDD0@DB8PR02MB5611.eurprd02.prod.outlook.com> <F7E5836A-4C7A-4A1A-B769-65EADE2C8F5C@gmail.com> <7d909ae3-a830-1270-6920-fa088a56525e@nwtime.org> <6C9832A9-E18B-4DE2-934F-9E471FC22F7B@akamai.com> <bc7920e2-dc81-ba7f-ec24-7926cda8589d@nwtime.org>
From: kristof.teichel@ptb.de
To: NTP WG <ntp@ietf.org>
Message-ID: <OFF6FE7A91.279129DD-ONC125854D.00379455-C125854D.0038D979@ptb.de>
Date: Fri, 17 Apr 2020 12:20:56 +0200
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/w5nVRJxBQY9SvyemsLONM-9ShsM>
Subject: [Ntp] Antwort: Re: The bump, or why NTP v5 must specify impulse response
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, 17 Apr 2020 10:21:06 -0000
-----"ntp" <ntp-bounces@ietf.org> schrieb: -----
Von: "Dieter Sibold"
Gesendet von: "ntp"
Datum: 16.04.2020 19:29
Kopie: "Watson Ladd" <watsonbladd@gmail.com>, "NTP WG" <ntp@ietf.org>, "Doug Arnold" <doug.arnold@meinberg-usa.com>, "Daniel Franke" <dfoxfranke@gmail.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Betreff: Re: [Ntp] The bump, or why NTP v5 must specify impulse response
implementation that conforms to RFC5905 completely.
There are different use cases for potential clients. Some of them are
not well served with the current algorithm other are. A modular approach
would allow both: to apply an algorithm most suitable to the application
and to be compliant with the protocol spec.
Dieter
On 16 Apr 2020, at 11:58, Harlan Stenn wrote:
> On 4/15/2020 6:38 AM, Salz, Rich wrote:
>>> We had the same discussion at the transition from ntpv3 to ntpv4.
>>> If you do this, please do not call it NTP.
>>
>> Can you explain why 3->4 could still be called NTP but 4->5 should
>> not?
>
> You didn't quote enough context.
>
> NTP is a combination of two parts:
>
> - the protocol/packet structure
> - algorithmic and response behavior
>
> If you are only specifying the protocol in this new thing then it is
> dangerous/misleading/irresponsible to call this v5 document "NTP".
>
> It is only slightly less dangerous/misleading/irresponsible to call it
> "NTPv5 Protocol", regardless of whether or not there is also an "NTPv5
> Algorithms and Response Behavior".
>
> --
> Harlan Stenn <stenn@nwtime.org>
> http://networktimefoundation.org" rel="nofollow">http://networktimefoundation.org - be a member!
_______________________________________________
ntp mailing list
ntp@ietf.org
https://www.ietf.org/mailman/listinfo/ntp" rel="nofollow">https://www.ietf.org/mailman/listinfo/ntp
- [Ntp] The bump, or why NTP v5 must specify impuls… Watson Ladd
- Re: [Ntp] The bump, or why NTP v5 must specify im… Daniel Franke
- Re: [Ntp] The bump, or why NTP v5 must specify im… Watson Ladd
- Re: [Ntp] The bump, or why NTP v5 must specify im… Daniel Franke
- Re: [Ntp] The bump, or why NTP v5 must specify im… Daniel Franke
- Re: [Ntp] The bump, or why NTP v5 must specify im… Doug Arnold
- Re: [Ntp] The bump, or why NTP v5 must specify im… Miroslav Lichvar
- Re: [Ntp] The bump, or why NTP v5 must specify im… Dieter Sibold
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Salz, Rich
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Ulrich Windl
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Warner Losh
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Salz, Rich
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Harlan Stenn
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Kyle Rose
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Harlan Stenn
- Re: [Ntp] The bump, or why NTP v5 must specify im… Harlan Stenn
- Re: [Ntp] The bump, or why NTP v5 must specify im… Salz, Rich
- Re: [Ntp] The bump, or why NTP v5 must specify im… Harlan Stenn
- Re: [Ntp] The bump, or why NTP v5 must specify im… Tony Finch
- Re: [Ntp] The bump, or why NTP v5 must specify im… Harlan Stenn
- Re: [Ntp] The bump, or why NTP v5 must specify im… Kurt Roeckx
- Re: [Ntp] The bump, or why NTP v5 must specify im… Dieter Sibold
- Re: [Ntp] The bump, or why NTP v5 must specify im… Harlan Stenn
- Re: [Ntp] The bump, or why NTP v5 must specify im… Daniel Franke
- [Ntp] Antwort: Re: The bump, or why NTP v5 must s… kristof.teichel
- Re: [Ntp] The bump, or why NTP v5 must specify im… Harlan Stenn
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Doug Arnold
- Re: [Ntp] The bump, or why NTP v5 must specify im… Kurt Roeckx
- Re: [Ntp] The bump, or why NTP v5 must specify im… doug.arnold
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Daniel Franke
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Doug Arnold
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Warner Losh
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Daniel Franke
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Warner Losh
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Daniel Franke
- Re: [Ntp] The bump, or why NTP v5 must specify im… Hal Murray
- [Ntp] Antw: [EXT] Re: The bump, or why NTP v5 mus… Ulrich Windl
- [Ntp] Antwort: Re: The bump, or why NTP v5 must s… kristof.teichel
- Re: [Ntp] The bump, or why NTP v5 must specify im… Doug Arnold
- Re: [Ntp] Antwort: Re: The bump, or why NTP v5 mu… Doug Arnold
- Re: [Ntp] The bump, or why NTP v5 must specify im… Salz, Rich
- Re: [Ntp] The bump, or why NTP v5 must specify im… Philip Prindeville
- Re: [Ntp] The bump, or why NTP v5 must specify im… Doug Arnold
- Re: [Ntp] The bump, or why NTP v5 must specify im… Philip Prindeville
- Re: [Ntp] The bump, or why NTP v5 must specify im… Watson Ladd
- Re: [Ntp] The bump, or why NTP v5 must specify im… Harlan Stenn
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Ulrich Windl
- Re: [Ntp] The bump, or why NTP v5 must specify im… Watson Ladd
- [Ntp] Antw: [EXT] Re: The bump, or why NTP v5 mus… Ulrich Windl
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Dieter Sibold
- [Ntp] Antw: Re: [EXT] Re: The bump, or why NTP v5… Ulrich Windl
- Re: [Ntp] The bump, or why NTP v5 must specify im… Miroslav Lichvar
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … Miroslav Lichvar
- Re: [Ntp] The bump, or why NTP v5 must specify im… Danny Mayer
- Re: [Ntp] The bump, or why NTP v5 must specify im… Doug Arnold
- Re: [Ntp] The bump, or why NTP v5 must specify im… Philip Prindeville
- Re: [Ntp] The bump, or why NTP v5 must specify im… Kurt Roeckx
- [Ntp] Antw: [EXT] Re: The bump, or why NTP v5 mus… Ulrich Windl
- Re: [Ntp] Antw: [EXT] Re: The bump, or why NTP v5… Hal Murray
- Re: [Ntp] Antw: [EXT] Re: The bump, or why NTP v5… Doug Arnold
- Re: [Ntp] [EXT] Re: The bump, or why NTP v5 must … David L. Mills
- Re: [Ntp] The bump, or why NTP v5 must specify im… Heiko Gerstung
- Re: [Ntp] The bump, or why NTP v5 must specify im… Watson Ladd