Joe, I wanted to run an idea by you. We all know that IPv4 fragmentation has problems because of the 16-bit ID field. So, why not insert an IPv6 Fragment Header between the IPv4 header and the upper layer protocol data, then use IPv6-style fragmentation instead of IPv4 fragmentation?
So, the IPv4 Protocol field would be set to '44', the IPv4 header would be followed by an IPv6 Fragment Header, and the "Next Header" field in the IPv6 Fragment Header would be set to the Protocol Number for the upper layer protocol. Then, upon fragmentation, each fragment would have an IPv4 header followed by an IPv6 Fragment Header. This format is shown in Figure 6 in Appendix A of the AERO draft: https://datatracker.ietf.org/doc/draft-templin-aerolink/ Does this look like something that should be broken out and put into a little standalone document? Thanks - Fred _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
