The following errata report has been submitted for RFC9347,
"Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP)
and Its Use for IP Traffic Flow Security (IP-TFS)".
--
You may review the report below and at:
https://www.rfc-editor.org/er
On Mon, 22 Jul 2024, RFC Errata System wrote:
Subject: [IPsec] [Technical Errata Reported] RFC9347 (8042)
The following errata report has been submitted for RFC9347,
"Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its
Use for IP Traffic Flow Security (IP-TFS)".
On Mon, Jul 22, 2024 at 04:20:39PM -0400, Paul Wouters wrote:
> On Mon, 22 Jul 2024, RFC Errata System wrote:
>
> > Subject: [IPsec] [Technical Errata Reported] RFC9347 (8042)
> >
> > The following errata report has been submitted for RFC9347,
> > "Aggregation and Fragmentation Mode for Encapsula
Paul,
FYI, the "Original text" in this report has been updated to match the actual
RFC (https://www.rfc-editor.org/rfc/rfc9347.html#section-7.2).
As discussed, this line contains 2 errors (the range and 'Reserved' where it
should have been 'Unassigned').
See https://www.rfc-editor.org/errata/
The following errata report has been verified for RFC9347,
"Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP)
and Its Use for IP Traffic Flow Security (IP-TFS)".
--
You may review the report below and at:
https://www.rfc-editor.org/er
On Mon, 22 Jul 2024, Alice Russo wrote:
Paul,
FYI, the "Original text" in this report has been updated to match the actual
RFC (https://www.rfc-editor.org/rfc/rfc9347.html#section-7.2).
As discussed, this line contains 2 errors (the range and 'Reserved' where it
should have been 'Unassigned'
Hi all,
The registry now reads as follows:
AGGFRAG_PAYLOAD Sub-Types
Registration Procedure(s): Expert Review
Expert(s): Christian Hopps
Reference: [RFC9347][RFC Errata 8042]
Sub-TypeNameReference
0 Non-Congestion-Control Format [RFC9347]
1 Congestion Control Format
