Re: [Editorial Errata Reported] RFC9114 (7702)

Rebecca VanRheenen <rvanrheenen@amsl.com> Wed, 15 November 2023 05:01 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: [Editorial Errata Reported] RFC9114 (7702)
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20231115032323.0E4E4199608D@rfcpa.amsl.com>
Date: Tue, 14 Nov 2023 21:01:03 -0800
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Mike Bishop <mbishop@evequefou.be>, quic@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF9C63EC-6771-4872-B625-A31FEDC96FFE@amsl.com>
References: <20231115032323.0E4E4199608D@rfcpa.amsl.com>
To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RsI4dwDWmuCSLrIQ1-7FqXV-C8w>
Precedence: list

Hi Zahed, 

We are unable to verify this erratum that the submitter marked as editorial.  
Please note that we have changed the “Type” of the following errata 
report to “Technical”.  As Stream Approver, please review and set the 
Status and Type accordingly (see the definitions at 
https://www.rfc-editor.org/errata-definitions/).

Note: We updated the line breaks in the report to improve readability. We suggest 
that you review the report at the link below rather than review the email.

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

Please see https://www.rfc-editor.org/how-to-verify/ for further 
information on how to verify errata reports.

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php.

Thank you.

RFC Editor/rv


> On Nov 14, 2023, at 7:23 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC9114,
> "HTTP/3".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7702
> 
> --------------------------------------
> Type: Editorial
> Reported by: Lucas Pardue <lucaspardue.24.7@gmail.com>
> 
> Section: 10.7
> 
> Original Text
> -------------
> Where
> HTTP/2
> employs
> PADDING
> frames
> and
> Padding
> fields
> in
> other
> frames
> to
> make
> a
> connection
> more
> resistant
> to
> traffic
> analysis,
> HTTP/3
> can
> either
> rely
> on
> transport-layer
> padding
> or
> employ
> the
> reserved
> frame
> and
> stream
> types
> discussed
> in
> Sections
> 7.2.8
> and
> 6.2.3.
> 
> Corrected Text
> --------------
> Where
> HTTP/2
> employs
> Padding
> fields
> in
> some
> frames
> to
> make
> a
> connection
> more
> resistant
> to
> traffic
> analysis,
> HTTP/3
> can
> either
> rely
> on
> transport-layer
> padding
> or
> employ
> the
> reserved
> frame
> and
> stream
> types
> discussed
> in
> Sections
> 7.2.8
> and
> 6.2.3.
> 
> Notes
> -----
> HTTP/2 doesn't define PADDING frames
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC9114 (draft-ietf-quic-http-34)
> --------------------------------------
> Title               : HTTP/3
> Publication Date    : June 2022
> Author(s)           : M. Bishop, Ed.
> Category            : PROPOSED STANDARD
> Source              : QUIC
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
>

[Editorial Errata Reported] RFC9114 (7702) RFC Errata System
Re: [Editorial Errata Reported] RFC9114 (7702) Rebecca VanRheenen