Thank you, Michael, for your report. I would though slightly modify your corrected text into:
"Translating an IPv4 packet to carry it across the MAP domain will increase its size (typically either 20 or 28 bytes)." -éric On 12/10/2022, 15:44, "RFC Errata System" <[email protected]> wrote: The following errata report has been submitted for RFC7599, "Mapping of Address and Port using Translation (MAP-T)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7160 -------------------------------------- Type: Technical Reported by: Michael Overcash <[email protected]> Section: 10.1 Original Text ------------- Translating an IPv4 packet to carry it across the MAP domain will increase its size (typically by 20 bytes). Corrected Text -------------- Translating an IPv4 packet to carry it across the MAP domain will increase its size (typically by 28 bytes). Notes ----- In the context of MTU, it is important to account for packet fragmentation. If an IPv4 packet is fragmented, the size will increase by 28 bytes during translation. The IPv6 header is 20 bytes larger than the IPv4 header, and in addition the 8 byte IPv6 Fragmentation Header must be added. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7599 (draft-ietf-softwire-map-t-08) -------------------------------------- Title : Mapping of Address and Port using Translation (MAP-T) Publication Date : July 2015 Author(s) : X. Li, C. Bao, W. Dec, Ed., O. Troan, S. Matsushima, T. Murakami Category : PROPOSED STANDARD Source : Softwires Area : Internet Stream : IETF Verifying Party : IESG _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
