I did look at the protocols involved here; the ingress does add headers but doesn’t appear to handle fragmentation.
That’s a non-starter if you want your packets to traverse a network because people WILL hand you 1280-byte packets, so what will you do?
FWIW, we have been insisting on this point (and others) since they first tried to push EH insertion in draft-ietf-6man-segment-routing-header.THey removed it from *that* document, but they keep trying to push similar ideas in other documents.
Well its seems simple to me - they need a plan for fragmentation or it’s simply a nonstarter because they can’t support 1280-B packets traversing the network.
No amount of “but this is what the user wants” translates to “they want their packets dropped silently”.
Joe |
