RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 9481, "Certificate Management Protocol (CMP) Algorithms", November 2023

Source of RFC: lamps (sec)

Errata ID: 7800
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML

Reported By: Russ Housley
Date Reported: 2024-02-07
Verifier Name: RFC Editor
Date Verified: 2024-02-07

Section 6.2.3 says:

   The KMAC algorithm is defined in [RFC8702] and FIPS SP 800-185
   [NIST.SP.800-185]].

It should say:

   The KMAC algorithm is defined in [RFC8702] and NIST SP 800-185
   [NIST.SP.800-185].

Notes:

Correct two errors. First, the referenced document is a Special Publication, not a FIPS. Second, there are two closing brackets, but there should only be one.

Status: Held for Document Update (1)

RFC 9481, "Certificate Management Protocol (CMP) Algorithms", November 2023

Source of RFC: lamps (sec)

Errata ID: 8018
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Carsten Bormann
Date Reported: 2024-07-03
Held for Document Update by: RFC Editor
Date Held: 2024-07-09

Section 10 says:

   [NIST.FIPS.180-4]
              Dang, Q. H. and NIST, "Secure Hash Standard", NIST Federal
              Information Processing Standards Publications 180-4,
              DOI 10.6028/NIST.FIPS.180-4, July 2015,
              <https://nvlpubs.nist.gov/nistpubs/FIPS/
              NIST.FIPS.180-4.pdf>.

It should say:

   [NIST.FIPS.180-4]
              Dang, Q. H., "Secure Hash Standard", NIST Federal
              Information Processing Standards Publications 180-4,
              DOI 10.6028/NIST.FIPS.180-4, July 2015,
              <https://nvlpubs.nist.gov/nistpubs/FIPS/
              NIST.FIPS.180-4.pdf>.

Notes:

The references section contains several references (the given one is just the first example) that treat NIST like a human author under several.
In this example, the mistake is directly imported from bib.ietf.org for NIST.FIPS.180-4

(This should become "Hold for Document Update", as it is unlikely to cause confusion, just a few raised eyebrows.)

--VERIFIER NOTES--
See:
https://github.com/ietf-tools/bibxml-service/issues/262
https://github.com/ietf-tools/bibxml-service/issues/418

Report New Errata



Advanced Search