< draft-ietf-tcplw-sack-01.txt		draft-ietf-tcplw-sack-02.txt >
	Internet Engineering Task Force TCPLW WG		Internet Engineering Task Force TCPLW WG
	INTERNET-DRAFT Mathis/Mahdavi/Floyd/Romanow		INTERNET-DRAFT Mathis/Mahdavi/Floyd/Romanow
	Draft-ietf-tcplw-sack-01.txt PSC/LBL/Sun		Draft-ietf-tcplw-sack-02.txt PSC/LBL/Sun
	19 April 1996		26 April 1996
	Expires: 29/7/96		Expires: 29/7/96
	TCP Selective Acknowledgment Options		TCP Selective Acknowledgment Options
	STATUS OF THIS MEMO		STATUS OF THIS MEMO
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	skipping to change at page 5, line 47 ¶		skipping to change at page 5, line 47 ¶
	as possible in the SACK option. Note that the maximum		as possible in the SACK option. Note that the maximum
	available option space may not be sufficient to report all		available option space may not be sufficient to report all
	blocks present in the receiver's queue.		blocks present in the receiver's queue.
	* The SACK option SHOULD be filled out by repeating the most		* The SACK option SHOULD be filled out by repeating the most
	recently reported SACK blocks (based on first SACK blocks in		recently reported SACK blocks (based on first SACK blocks in
	previous SACK options) that are not subsets of a SACK block		previous SACK options) that are not subsets of a SACK block
	already included in the SACK option being constructed. This		already included in the SACK option being constructed. This
	assures that in normal operation, any segment remaining part		assures that in normal operation, any segment remaining part
	of a non-contiguous block of data held by the data receiver is		of a non-contiguous block of data held by the data receiver is
	reported in at least three successive SACK options, ever for		reported in at least three successive SACK options, even for
	large-window TCP implementations [RFC1323]).		large-window TCP implementations [RFC1323]). After the first
			SACK block, the following SACK blocks in the SACK option may be
			listed in arbitrary order.
	It is very important that the SACK option always reports		It is very important that the SACK option always reports
	the block containing the most recently received segment, because		the block containing the most recently received segment, because
	this provides the sender with the most up-to-date information		this provides the sender with the most up-to-date information
	about the state of the network and the data receiver's queue.		about the state of the network and the data receiver's queue.
	5. INTERPRETING THE SACK OPTION AND RETRANSMISSION STRATEGY:		5. INTERPRETING THE SACK OPTION AND RETRANSMISSION STRATEGY:
	DATA SENDER BEHAVIOR		DATA SENDER BEHAVIOR
	When receiving an ACK containing a SACK option, the data sender		When receiving an ACK containing a SACK option, the data sender
End of changes. 2 change blocks.
	4 lines changed or deleted		6 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/