[Ntp] [Errata Verified] RFC9249 (7401)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 21 March 2023 13:46 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 6BED7C1524DD; Tue, 21 Mar 2023 06:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 hy5kK6IqeuD1; Tue, 21 Mar 2023 06:46:21 -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 82C51C151535; Tue, 21 Mar 2023 06:46:21 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 4089E7FDF1; Tue, 21 Mar 2023 06:46:21 -0700 (PDT)
To: maurice.angermann@siemens.com, eric.wu@huawei.com, dhruv.ietf@gmail.com, ankit.ietf@gmail.com, anil.ietf@gmail.com, yi.z.zhao@ericsson.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ek.ietf@gmail.com, iesg@ietf.org, ntp@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230321134621.4089E7FDF1@rfcpa.amsl.com>
Date: Tue, 21 Mar 2023 06:46:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/pAyrxkPfyc-_cWjLTO26GYq1-Ys>
Subject: [Ntp] [Errata Verified] 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 13:46:25 -0000

The following errata report has been verified for RFC9249,
"A YANG Data Model for NTP". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7401

--------------------------------------
Status: Verified
Type: Technical

Reported by: Maurice Angermann <maurice.angermann@siemens.com>
Date Reported: 2023-03-21
Verified by: Erik Kline (IESG)

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.

--------------------------------------
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