Found 1 record.

Status: Reported (1)

RFC 9458, "Oblivious HTTP", January 2024

Errata ID: 7781
Status: Reported
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Dan Gould
Date Reported: 2024-01-25

Appendix A says:

   The AEAD Seal() function is then used to encrypt the response, which
   is added to the randomized nonce value to produce the Encapsulated
   Response:

   c789e7151fcba46158ca84b04464910d86f9013e404feea014e7be4a441f234f
   857fbd

   The Oblivious Gateway Resource constructs a response with the same
   content:

   HTTP/1.1 200 OK
   Date: Wed, 27 Jan 2021 04:45:07 GMT
   Cache-Control: private, no-store
   Content-Type: message/ohttp-res
   Content-Length: 38

   <content is the Encapsulated Response>

It should say:

   The AEAD Seal() function is then used to encrypt the response, which
   is added to the randomized nonce value to produce the Encapsulated
   Response:

   c789e7151fcba46158ca84b04464910d86f9013e404feea014e7be4a441f234f
   857fbd

   The Oblivious Gateway Resource constructs a response with the same
   content:

   HTTP/1.1 200 OK
   Date: Wed, 27 Jan 2021 04:45:07 GMT
   Cache-Control: private, no-store
   Content-Type: message/ohttp-res
   Content-Length: 35

   <content is the Encapsulated Response>

Notes:

The Content-Length header in the example response is set to 38 while the given Encapsulated Response (c789e7151fcba46158ca84b04464910d86f9013e404feea014e7be4a441f234f
857fbd) has a length of 35

Report New Errata