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-Type Name Reference 0 Non-Congestion-Control Format [RFC9347] 1 Congestion Control Format [RFC9347] 2-255 Unassigned Please see https://www.iana.org/assignments/esp-aggfrag-payload thanks, Amanda On Tue Jul 23 00:31:12 2024, rfc-edi...@rfc-editor.org wrote: > 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/errata/eid8042 > > -------------------------------------- > Status: Verified > Type: Technical > > Reported by: Antony Antony <antony.ant...@secunet.com> > Date Reported: 2024-07-22 > Verified by: Paul Wouters (IESG) > > Section: 7.2 > > Original Text > ------------- > 3-255 Reserved > > 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"? > > -------------------------------------- > 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
