Re: Issue with Forward-TSN-Chunks containing high cum_tsn

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 17, 2017 at 02:07:52PM +0100, Julian Cordes wrote:
> When a FORWARD-TSN-Chunk with a relative high cum-tsn-value is injected
> then the linux kernel ignores this valid FORWARD-TSN-Chunk.
> It should instead send an SACK-Chunk where the cum_tsn is equal to the
> cum_tsn specified in the FORWARD-TSN.

You mean, with the cum_tsn specified on the *injected* FORWARD-TSN.
Is that so?

> 
> Testscript available at:
> https://github.com/nplab/PR_SCTP_Testsuite/blob/master/forward-tsn/receiver-side-implementation/receiver-side-implementation-11.pkt


--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Networking Development]     [Linux OMAP]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux