Of course i suppose any solution that involves path MTU discovery might
sometimes (for un/misconfigured hosts) incur an extra (host)<->(detour
edge router) exchange as the detour router says "nope, ain't gonna take a
1500 byte packet" & the host resends.
neal
On Thu, 29 Oct 1998, Eric Hoffman wrote:
>
> 1) we can take advantage of the fact that most TCP traffic isn't
> "two-way" (ie doesn't have data and acks together) and overload the
> acknowledgement number to hold the destination IP address. We could do
> the same thing with the sequence number in the ACK direction, but its
> unlikely that these packets will be MTU sized.
>
> wont someone have to have the necessary state in order to reconstitute
> the correct sequence number before handing it off to the destination
> host?
>
> i very much hate to bring up the possibility, but it might be better
> to explicitly label flows and recover necessary forwarding state based
> on the label, rather than exploit a series of special cases to cram a
> few bits here and there in the original packet
>
> of course managing this state (distributed forwarding cache) is a
> pretty severe pain pain in the ass
>