Re: [tcpm] New I-D posted : draft-moncaster-tcpm-rcv-cheat-00 - (asymmetry)

[Gorry Fairhurst <[e-mail]>]

John Heffner wrote:

> Anantha Ramaiah (ananth) wrote:
>
>>> is at odds with RFC 2581, which says:
>>>
>>>> Out-of-order data segments SHOULD be acknowledged immediately, in 
>>>> order to accelerate loss recovery.
>>>
>>> ...although I wonder why this is only a SHOULD, and not a MUST, and 
>>> herewith suggest to change this in 2581bis, unless there's a good 
>>> reason not to do so.
>>
<Snip>

>
> Paths with severe asymmetry may want to thin ACKs.  There were some 
> papers on this in the mid to late 90's coming out of work with 
> satellites and ADSL.
>
These arguments are in RFC 3449, for reference if you wish to go there.

If you expect receivers to ALWAYS generate specific ACKs, the RFC3449 
mitigations will give you some unexpected shocks (i.e. if you try to 
read more into the ACK stream than the TCP sender needed to clock out 
the data).

<Snip>

Gorry Fairhurst

_______________________________________________
tcpm mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/tcpm