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/errata/eid8042 -------------------------------------- Type: Technical Reported by: Antony Antony <antony.ant...@secunet.com> Section: 7.2 Original Text ------------- 3-255 Unassigned Corrected Text -------------- 2-255 Unassigned Notes ----- The same section, in the previous line, states "1 Congestion Control Format RFC 9347" so 2 is not covered in the registry. It's likely meant to be "Unassigned"? 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. -------------------------------------- RFC9347 (draft-ietf-ipsecme-iptfs-19) -------------------------------------- Title : Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) Publication Date : January 2023 Author(s) : C. Hopps Category : PROPOSED STANDARD Source : IP Security Maintenance and Extensions Stream : IETF Verifying Party : IESG _______________________________________________ IPsec mailing list -- ipsec@ietf.org To unsubscribe send an email to ipsec-le...@ietf.org
