RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (3)

RFC 7518, "JSON Web Algorithms (JWA)", May 2015

Note: This RFC has been updated by RFC 9864

Source of RFC: jose (sec)

Errata ID: 6612
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Sebastián Ramírez
Date Reported: 2021-06-16
Verifier Name: Benjamin Kaduk
Date Verified: 2021-06-25

Section .4 says:

   2.  Turn R and S into octet sequences in big-endian order, with each
       array being be 32 octets long.  The octet sequence
       representations MUST NOT be shortened to omit any leading zero
       octets contained in the values.

It should say:

   2.  Turn R and S into octet sequences in big-endian order, with each
       array being 32 octets long.  The octet sequence
       representations MUST NOT be shortened to omit any leading zero
       octets contained in the values.

Notes:

"being be" should be changed to "being"

Errata ID: 8568
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Sören Sprößig
Date Reported: 2025-09-08
Verifier Name: RFC Editor
Date Verified: 2025-09-12

Section 3.2 says:

(This requirement is based on Section 5.3.4 (Security Effect of the HMAC Key) of 
NIST SP 800-117 [NIST.800-107], which states that the effective security 
strength is the minimum of the security strength of the key and two times the 
size of the internal hash value.)

It should say:

(This requirement is based on Section 5.3.4 (Security Effect of the HMAC Key) of 
NIST SP 800-107 [NIST.800-107], which states that the effective security 
strength is the minimum of the security strength of the key and two times the 
size of the internal hash value.)

Notes:

NIST SP 800-117 was SCAP, 800-107 is the correct one (as linked).

Errata ID: 8747
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Filip Skokan
Date Reported: 2026-02-08
Verifier Name: RFC Editor
Date Verified: 2026-03-02

Section 7.1.1 says:

Algorithm Analysis Documents(s):

It should say:

Algorithm Analysis Document(s):

Notes:

This is a typo in the registration template. The template is shared between JWS and JWE and the JWS document does not have this typo. The IANA registry itself does not contain this typo either.

Status: Reported (1)

RFC 7518, "JSON Web Algorithms (JWA)", May 2015

Note: This RFC has been updated by RFC 9864

Source of RFC: jose (sec)

Errata ID: 8526
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Benjamin Hurst
Date Reported: 2025-08-05

Section 3.4.5 says:

|  Compression of RTCP: No IETF-defined header compression method
      compress RTCP; however, if such methods are developed in the
|     future, these methods must take Reduced-Size RTCP in account.

It should say:

|Compression of RTCP: No IETF-defined header compression methods
      compress RTCP; however, if such methods are developed in the
|     future, these methods must take Reduced-Size RTCP into account.

Notes:

Note: this also applies to any changes to files in [RFC2119]

Report New Errata



Advanced Search