On 3/21/24 14:59, Tom Herbert wrote:
On Thu, Mar 21, 2024 at 2:36 PM Brian E Carpenter
<[email protected]> wrote:
On 22-Mar-24 09:04, Tom Herbert wrote:
On Thu, Mar 21, 2024 at 12:46 PM Templin (US), Fred L
<[email protected]> wrote:
Brian,
Why should the IETF spend effort on upgrading IPv4 capabilities at this point?
For air/land/sea/space mobile Internetworking, we expect to engage steady-state
IP
fragmentation over some paths, but IPv4 will still be in the picture for a long
time to
come and IPv4 fragmentation has known limitations (e.g., RFC4963). IPv4
fragmentation
using the IPv6 Fragment Header (adapted for IPv4) would address many of the
issues.
This is just to name one example. Another example is adapting IPv6 HBH options
to
carry IP parcels and Advanced Jumbos in IPv4 packets for operation over networks
where IPv4 will still be used for the long term.
IPv4 is going to be around for a long time in many networks, so making it work
more like IPv6 seems like a useful improvement.
Yes, we still have IPv4 users that need the capabilities. If everyone
were on IPv6 we wouldn't need this.
So this proposal hinders IPv6 adoption. I think it would lead to an
"interesting" IETF Last Call discussion.
Increasing adoption by crippling IPv4??? No, sir, the opposite is a
better approach. Improve IPv6, improve IPv4. This is the way to go.
Hi Brian,
Well I knew going in this would be provocative :-)
Actually, I believe this accelerates IPv6 adoption. We're essentially
unifying portions IPv4 and IPv6 so that makes a complete transition
that much easier. If people adopt the hacky alternatives I mentioned
then it's likely they'll just propagate those into IPv6 (that's
another effect we've seen, some people "adopt" IPv6 but still treat it
like IPv4). Besides, we've been working on IPv6 for what, thirty
years, I really doubt *this* is the thing that will get the blame for
how long adoption is taking :-).
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
