Hi Jonathan,
> On May 6, 2016, at 06:44 , Jonathan Morton <[email protected]> wrote:
>
>
>> On 6 May, 2016, at 07:35, Dave Taht <[email protected]> wrote:
>>
>> this would be a pretty nifty feature for cake to have in this hostile
>> universe.
>
> Yes, but difficult to implement since the trailing fragments lose the
> proto/port information, and thus get sorted into a different queue than the
> leading fragment. We would essentially need to implement the same tracking
> mechanisms as for actual reassembly.
But the receiver needs to be able to re-segment the fragments so all
required information needs to be there; what about looking at src and dst
address and the MF flag in the header as well as the fragment offset and scrape
proto/port from the leading fragment and “virtually” apply it to all following
fragments, that way cake will do the right thing. All of this might be too
costly in implementation and computation to be feasible…
Best Regards
Sebastian
>
> - Jonathan Morton
>
> _______________________________________________
> Cake mailing list
> [email protected]
> https://lists.bufferbloat.net/listinfo/cake
_______________________________________________
Cake mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/cake
