IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: [Last-Call] Last Call: <draft-ietf-ntp-yang-data-model-10.txt> (A YANG Data Model for NTP) to Proposed Standard

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 23 February 2021 08:21 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.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 A3E033A2858 for <ntp@ietfa.amsl.com>; Tue, 23 Feb 2021 00:21:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 yyDe0zf2TQOw for <ntp@ietfa.amsl.com>; Tue, 23 Feb 2021 00:21:33 -0800 (PST)
Received: from mx1.uni-regensburg.de (mx1.uni-regensburg.de [194.94.157.146]) (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 200103A2854 for <ntp@ietf.org>; Tue, 23 Feb 2021 00:21:32 -0800 (PST)
Received: from mx1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 90AA8600004D for <ntp@ietf.org>; Tue, 23 Feb 2021 09:21:29 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx1.uni-regensburg.de (Postfix) with ESMTP id D04BC6000050 for <ntp@ietf.org>; Tue, 23 Feb 2021 09:21:26 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 23 Feb 2021 09:21:26 +0100
Message-Id: <6034BB03020000A10003F3A1@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Tue, 23 Feb 2021 09:21:23 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: martin.burnicki=40meinberg.de@dmarc.ietf.org, "ntp@ietf.org" <ntp@ietf.org>
References: <161195994417.2651.6499166797756243533@ietfa.amsl.com> <CAB75xn5CQr2yg7wWZHj-sJM7WaaTJK5NF0pzzLhqmx5hHf8GiQ@mail.gmail.com> <60266E12.6070207@btconnect.com> <602A611E.4020306@btconnect.com> <CAB75xn7QVL+F_5bQ8roZYakbADgQ06pChb0ei7Oaf0=eqLu7Mg@mail.gmail.com> <602D0CF9.9090404@btconnect.com> <602F9344.7000808@btconnect.com> <606b2602-a7ba-c6f7-c6d3-5883721a1575@pdmconsulting.net> <7B08EF68-0A3D-49BD-B6F0-206E4E6FF112@akamai.com> <602FE8A5.2090906@btconnect.com> <04577fe6-3704-21c4-e541-a7a82c198ec4@huitema.net> <177cd49b-8672-0b8e-a3ba-43c0b3bb9ea9@meinberg.de>
In-Reply-To: <177cd49b-8672-0b8e-a3ba-43c0b3bb9ea9@meinberg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/igE--TWl7Nm3LHPF_JefBw-O5eI>
Subject: [Ntp] Antw: [EXT] Re: [Last-Call] Last Call: <draft-ietf-ntp-yang-data-model-10.txt> (A YANG Data Model for NTP) to Proposed Standard
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: Tue, 23 Feb 2021 08:21:36 -0000

>>> Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org> schrieb am
22.02.2021 um 09:39 in Nachricht
<177cd49b-8672-0b8e-a3ba-43c0b3bb9ea9@meinberg.de>:
> Christian Huitema wrote:
>> There is another problem. Because MD5 is deprecated, some software 
>> development organizations have checks that prevent use of MD5. The test 
>> suites will include such checks, and the software will normally not ship 
>> if the checks detect presence of MD5 in the product. Of course there are 
>> ways around, but they are not quite as simple as replacing MD5 by 
>> SHA256, even for those "non crypto" cases.
> 
> Imaging SHA-1 wasn't supported anymore at all, how would you be able to 
> track the history of commit hashes in a git repository, which are based 
> on SHA-1?
> 
> So isn't it a really silly approach to stop supporting certain features 
> in general just because they aren't appropriate anymore for certain tasks?

I agree: There are even valid use cases for CRC-32.

> 
> Martin
> -- 
> Martin Burnicki
> 
> Senior Software Engineer
> 
> MEINBERG Funkuhren GmbH & Co. KG
> Email: martin.burnicki@meinberg.de 
> Phone: +49 5281 9309-414
> Linkedin: https://www.linkedin.com/in/martinburnicki/ 
> 
> Lange Wand 9, 31812 Bad Pyrmont, Germany
> Amtsgericht Hannover 17HRA 100322
> Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, 
> Andre Hartmann, Heiko Gerstung
> Websites: https://www.meinberg.de  https://www.meinbergglobal.com 
> Training: https://www.meinberg.academy

v2.23.0 | Report a Bug | By Email