[Ntp] [Technical Errata Reported] RFC9249 (7401)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 21 March 2023 12:09 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 8B0C7C1522C6 for <ntp@ietfa.amsl.com>; Tue, 21 Mar 2023 05:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NsPJvmtgLuDX for <ntp@ietfa.amsl.com>; Tue, 21 Mar 2023 05:09:40 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBF0CC14CE2C for <ntp@ietf.org>; Tue, 21 Mar 2023 05:09:40 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 968D07FDF1; Tue, 21 Mar 2023 05:09:40 -0700 (PDT)
To: eric.wu@huawei.com, dhruv.ietf@gmail.com, ankit.ietf@gmail.com, anil.ietf@gmail.com, yi.z.zhao@ericsson.com, ek.ietf@gmail.com, evyncke@cisco.com, odonoghue@isoc.org, dsibold.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: maurice.angermann@siemens.com, ntp@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230321120940.968D07FDF1@rfcpa.amsl.com>
Date: Tue, 21 Mar 2023 05:09:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/qstGnifxi7zESA4ttGLc7S8KDMA>
Subject: [Ntp] [Technical Errata Reported] RFC9249 (7401)
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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, 21 Mar 2023 12:09:44 -0000
The following errata report has been submitted for RFC9249, "A YANG Data Model for NTP". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7401 -------------------------------------- Type: Technical Reported by: Maurice Angermann <maurice.angermann@siemens.com> Section: 8 Original Text ------------- identity hmac-sha-256 { description "HMAC-SHA-256 authentication algorithm"; reference "SHS: Secure Hash Standard (SHS) (FIPS PUB 180-4)"; } identity hmac-sha-384 { description "HMAC-SHA-384 authentication algorithm"; reference "SHS: Secure Hash Standard (SHS) (FIPS PUB 180-4)"; } identity hmac-sha-512 { description "HMAC-SHA-512 authentication algorithm"; reference "SHS: Secure Hash Standard (SHS) (FIPS PUB 180-4)"; } Corrected Text -------------- identity hmac-sha-256 { base crypto-algorithm; description "HMAC-SHA-256 authentication algorithm"; reference "SHS: Secure Hash Standard (SHS) (FIPS PUB 180-4)"; } identity hmac-sha-384 { base crypto-algorithm; description "HMAC-SHA-384 authentication algorithm"; reference "SHS: Secure Hash Standard (SHS) (FIPS PUB 180-4)"; } identity hmac-sha-512 { base crypto-algorithm; description "HMAC-SHA-512 authentication algorithm"; reference "SHS: Secure Hash Standard (SHS) (FIPS PUB 180-4)"; } Notes ----- The identity definitions of "hmac-sha-256", "hmac-sha-384" and "hmac-sha-512" lack the "base crypto-algorithm;" statement and therefore basically cannot be used in the scope of ietf-ntp@2022-07-05.yang. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC9249 (draft-ietf-ntp-yang-data-model-17) -------------------------------------- Title : A YANG Data Model for NTP Publication Date : July 2022 Author(s) : N. Wu, D. Dhody, Ed., A. Sinha, Ed., A. Kumar S N, Y. Zhao Category : PROPOSED STANDARD Source : Network Time Protocols Area : Internet Stream : IETF Verifying Party : IESG
- [Ntp] [Technical Errata Reported] RFC9249 (7401) RFC Errata System
- Re: [Ntp] [Technical Errata Reported] RFC9249 (74… Dhruv Dhody