RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 8188, "Encrypted Content-Encoding for HTTP", June 2017

Source of RFC: httpbis (art)

Errata ID: 5051
Status: Verified
Type: Editorial

Reported By: Julian Reschke
Date Reported: 2017-06-24
Verifier Name: RFC Editor
Date Verified: 2017-06-24

Section 6.1 says:

   [FIPS180-4]
              National Institute of Standards and Technology, "Secure
              Hash Standard (SHS)", FIPS PUB 180-4,
              DOI 10.6028/NIST.FIPS180-4, August 2015,
              <http://nvlpubs.nist.gov/nistpubs/FIPS/
              NIST.FIPS.180-4.pdf>.

It should say:

   [FIPS180-4]
              National Institute of Standards and Technology, "Secure
              Hash Standard (SHS)", FIPS PUB 180-4,
              DOI 10.6028/NIST.FIPS.180-4, August 2015,
              <http://nvlpubs.nist.gov/nistpubs/FIPS/
              NIST.FIPS.180-4.pdf>.

Notes:

(incorrect DOI)

Status: Reported (1)

RFC 8188, "Encrypted Content-Encoding for HTTP", June 2017

Source of RFC: httpbis (art)

Errata ID: 5516
Status: Reported
Type: Technical

Reported By: Incorrect Content-Length header value in example
Date Reported: 2018-10-05

Section 3.1 says:

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 54
Content-Encoding: aes128gcm

I1BsxtFttlv3u_Oo94xnmwAAEAAA-NAVub2qFgBEuQKRapoZu-IxkIva3MEB1PD-
ly8Thjg

It should say:

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 53
Content-Encoding: aes128gcm

I1BsxtFttlv3u_Oo94xnmwAAEAAA-NAVub2qFgBEuQKRapoZu-IxkIva3MEB1PD-
ly8Thjg

Notes:

16-bit encrypted payload
16-bit authentication tag
21-bit header

The other example, in Section 3.2, reports the correct content length of 53

Report New Errata