W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2022

[Errata Held for Document Update] RFC8188 (5516)

From: RFC Errata System <rfc-editor@rfc-editor.org>
Date: Wed, 9 Nov 2022 00:31:54 -0800 (PST)
To: dolan@voatz.com, martin.thomson@gmail.com
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
Message-Id: <20221109083154.DABE91FD20@rfcpa.amsl.com>
The following errata report has been held for document update 
for RFC8188, "Encrypted Content-Encoding for HTTP". 

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

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Dolan Murvihill <dolan@voatz.com>
Date Reported: 2018-10-05
Held by: Francesca Palombini (IESG)

Section: 3.1

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

I1BsxtFttlv3u_Oo94xnmwAAEAAA-NAVub2qFgBEuQKRapoZu-IxkIva3MEB1PD-
ly8Thjg

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

--------------------------------------
RFC8188 (draft-ietf-httpbis-encryption-encoding-09)
--------------------------------------
Title               : Encrypted Content-Encoding for HTTP
Publication Date    : June 2017
Author(s)           : M. Thomson
Category            : PROPOSED STANDARD
Source              : HTTP
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG
Received on Wednesday, 9 November 2022 08:32:08 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 1 February 2023 02:18:31 UTC