netdev - RE: TCP NewReno and single retransmit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1C9E7159@AcuExch.aculab.com>
Date:	Tue, 4 Nov 2014 09:56:49 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Neal Cardwell' <ncardwell@...gle.com>,
	Marcelo Ricardo Leitner <mleitner@...hat.com>
CC:	Yuchung Cheng <ycheng@...gle.com>, netdev <netdev@...r.kernel.org>,
	"Eric Dumazet" <edumazet@...gle.com>
Subject: RE: TCP NewReno and single retransmit

> Since there are no literal IETF-style "MUST" statements in RFC2582, I
> think the "MUST" in the code here is expressing the design philosophy
> behind the author. :-)

I wouldn't guarantee that the authors of any RFC (or other
standards document) managed to cover all possible cases.

	David