rfc9308v4.txt		rfc9308.txt
	skipping to change at line 241 ¶		skipping to change at line 241 ¶
	the routing infrastructure (in particular, load balancers) uses the		the routing infrastructure (in particular, load balancers) uses the
	address/port 4-tuple to direct traffic. Furthermore, middleboxes		address/port 4-tuple to direct traffic. Furthermore, middleboxes
	with functions other than address translation could still affect the		with functions other than address translation could still affect the
	path. In particular, some firewalls do not admit server traffic for		path. In particular, some firewalls do not admit server traffic for
	which the firewall has no recent state for a corresponding packet		which the firewall has no recent state for a corresponding packet
	sent from the client.		sent from the client.
	QUIC applications can adjust idle periods to manage the risk of		QUIC applications can adjust idle periods to manage the risk of
	timeout. Idle periods and the network idle timeout are distinct from		timeout. Idle periods and the network idle timeout are distinct from
	the connection idle timeout, which is defined as the minimum of		the connection idle timeout, which is defined as the minimum of
	either endpoint's idle timeout parameter; see Section 10.1 of		either endpoint's idle timeout parameter; see Section 10.1 of [QUIC].
	[QUIC]). There are three options:		There are three options:
	* Ignore the issue if the application-layer protocol consists only		* Ignore the issue if the application-layer protocol consists only
	of interactions with no or very short idle periods or if the		of interactions with no or very short idle periods or if the
	protocol's resistance to NAT rebinding is sufficient.		protocol's resistance to NAT rebinding is sufficient.
	* Ensure there are no long idle periods.		* Ensure there are no long idle periods.
	* Resume the session after a long idle period, using 0-RTT		* Resume the session after a long idle period, using 0-RTT
	resumption when appropriate.		resumption when appropriate.
	skipping to change at line 546 ¶		skipping to change at line 546 ¶
	after expiration of the idle timeout (see Section 10).		after expiration of the idle timeout (see Section 10).
	5. Packetization and Latency		5. Packetization and Latency
	QUIC exposes an interface that provides multiple streams to the		QUIC exposes an interface that provides multiple streams to the
	application; however, the application usually cannot control how data		application; however, the application usually cannot control how data
	transmitted over those streams is mapped into frames or how those		transmitted over those streams is mapped into frames or how those
	frames are bundled into packets.		frames are bundled into packets.
	By default, many implementations will try to pack STREAM frames from		By default, many implementations will try to pack STREAM frames from
	from one or more streams into each QUIC packet, in order to minimize		one or more streams into each QUIC packet, in order to minimize
	bandwidth consumption and computational costs (see Section 13 of		bandwidth consumption and computational costs (see Section 13 of
	[QUIC]). If there is not enough data available to fill a packet, an		[QUIC]). If there is not enough data available to fill a packet, an
	implementation might wait for a short time to optimize bandwidth		implementation might wait for a short time to optimize bandwidth
	efficiency instead of latency. This delay can either be		efficiency instead of latency. This delay can either be
	preconfigured or dynamically adjusted based on the observed sending		preconfigured or dynamically adjusted based on the observed sending
	pattern of the application.		pattern of the application.
	If the application requires low latency, with only small chunks of		If the application requires low latency, with only small chunks of
	data to send, it may be valuable to indicate to QUIC that all data		data to send, it may be valuable to indicate to QUIC that all data
	should be sent out immediately. Alternatively, if the application		should be sent out immediately. Alternatively, if the application
End of changes. 2 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48.