[net-next-2.6.git] / net / dccp / ccids / Kconfig

menu "DCCP CCIDs Configuration (EXPERIMENTAL)"
	depends on IP_DCCP && EXPERIMENTAL

config IP_DCCP_CCID2
	tristate "CCID2 (TCP-Like) (EXPERIMENTAL)"
	depends on IP_DCCP
	def_tristate IP_DCCP
	select IP_DCCP_ACKVEC
	---help---
	  CCID 2, TCP-like Congestion Control, denotes Additive Increase,
	  Multiplicative Decrease (AIMD) congestion control with behavior
	  modelled directly on TCP, including congestion window, slow start,
	  timeouts, and so forth [RFC 2581].  CCID 2 achieves maximum
	  bandwidth over the long term, consistent with the use of end-to-end
	  congestion control, but halves its congestion window in response to
	  each congestion event.  This leads to the abrupt rate changes
	  typical of TCP.  Applications should use CCID 2 if they prefer
	  maximum bandwidth utilization to steadiness of rate.  This is often
	  the case for applications that are not playing their data directly
	  to the user.  For example, a hypothetical application that
	  transferred files over DCCP, using application-level retransmissions
	  for lost packets, would prefer CCID 2 to CCID 3.  On-line games may
	  also prefer CCID 2.

	  CCID 2 is further described in:
	  http://www.icir.org/kohler/dccp/draft-ietf-dccp-ccid2-10.txt

	  This text was extracted from:
	  http://www.icir.org/kohler/dccp/draft-ietf-dccp-spec-13.txt

	  If in doubt, say M.

config IP_DCCP_CCID2_DEBUG
	  bool "CCID2 debug"
	  depends on IP_DCCP_CCID2
	  ---help---
	    Enable CCID2 debug messages.

	    If in doubt, say N.

config IP_DCCP_CCID3
	tristate "CCID3 (TCP-Friendly) (EXPERIMENTAL)"
	depends on IP_DCCP
	def_tristate IP_DCCP
	---help---
	  CCID 3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
	  rate-controlled congestion control mechanism.  TFRC is designed to
	  be reasonably fair when competing for bandwidth with TCP-like flows,
	  where a flow is "reasonably fair" if its sending rate is generally
	  within a factor of two of the sending rate of a TCP flow under the
	  same conditions.  However, TFRC has a much lower variation of
	  throughput over time compared with TCP, which makes CCID 3 more
	  suitable than CCID 2 for applications such streaming media where a
	  relatively smooth sending rate is of importance.

	  CCID 3 is further described in:

	  http://www.icir.org/kohler/dccp/draft-ietf-dccp-ccid3-11.txt.

	  The TFRC congestion control algorithms were initially described in
	  RFC 3448.

	  This text was extracted from:
	  http://www.icir.org/kohler/dccp/draft-ietf-dccp-spec-13.txt
	  
	  If in doubt, say M.

config IP_DCCP_TFRC_LIB
	depends on IP_DCCP_CCID3
	def_tristate IP_DCCP_CCID3

endmenu
Commit	Line	Data
7c657876 ACM	1	menu "DCCP CCIDs Configuration (EXPERIMENTAL)"
	2	depends on IP_DCCP && EXPERIMENTAL
	3
2a91aa39	4	config IP_DCCP_CCID2
057fc675	5	tristate "CCID2 (TCP-Like) (EXPERIMENTAL)"
2a91aa39	6	depends on IP_DCCP
057fc675	7	def_tristate IP_DCCP
2a91aa39 AB	8	select IP_DCCP_ACKVEC
	9	---help---
	10	CCID 2, TCP-like Congestion Control, denotes Additive Increase,
	11	Multiplicative Decrease (AIMD) congestion control with behavior
	12	modelled directly on TCP, including congestion window, slow start,
	13	timeouts, and so forth [RFC 2581]. CCID 2 achieves maximum
	14	bandwidth over the long term, consistent with the use of end-to-end
	15	congestion control, but halves its congestion window in response to
	16	each congestion event. This leads to the abrupt rate changes
	17	typical of TCP. Applications should use CCID 2 if they prefer
	18	maximum bandwidth utilization to steadiness of rate. This is often
	19	the case for applications that are not playing their data directly
	20	to the user. For example, a hypothetical application that
	21	transferred files over DCCP, using application-level retransmissions
	22	for lost packets, would prefer CCID 2 to CCID 3. On-line games may
	23	also prefer CCID 2.
	24
	25	CCID 2 is further described in:
	26	http://www.icir.org/kohler/dccp/draft-ietf-dccp-ccid2-10.txt
	27
	28	This text was extracted from:
	29	http://www.icir.org/kohler/dccp/draft-ietf-dccp-spec-13.txt
	30
	31	If in doubt, say M.
	32
8d424f6c AB	33	config IP_DCCP_CCID2_DEBUG
	34	bool "CCID2 debug"
	35	depends on IP_DCCP_CCID2
	36	---help---
	37	Enable CCID2 debug messages.
	38
	39	If in doubt, say N.
	40
7c657876	41	config IP_DCCP_CCID3
057fc675	42	tristate "CCID3 (TCP-Friendly) (EXPERIMENTAL)"
7c657876	43	depends on IP_DCCP
057fc675	44	def_tristate IP_DCCP
7c657876 ACM	45	---help---
	46	CCID 3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
	47	rate-controlled congestion control mechanism. TFRC is designed to
	48	be reasonably fair when competing for bandwidth with TCP-like flows,
	49	where a flow is "reasonably fair" if its sending rate is generally
	50	within a factor of two of the sending rate of a TCP flow under the
	51	same conditions. However, TFRC has a much lower variation of
	52	throughput over time compared with TCP, which makes CCID 3 more
	53	suitable than CCID 2 for applications such streaming media where a
	54	relatively smooth sending rate is of importance.
	55
2a91aa39 AB	56	CCID 3 is further described in:
	57
	58	http://www.icir.org/kohler/dccp/draft-ietf-dccp-ccid3-11.txt.
	59
	60	The TFRC congestion control algorithms were initially described in
	61	RFC 3448.
7c657876	62
2a91aa39 AB	63	This text was extracted from:
2a91aa39 AB	64	http://www.icir.org/kohler/dccp/draft-ietf-dccp-spec-13.txt
7c657876 ACM	65
	66	If in doubt, say M.
	67
5cea0ddc ACM	68	config IP_DCCP_TFRC_LIB
	69	depends on IP_DCCP_CCID3
	70	def_tristate IP_DCCP_CCID3
	71
7c657876	72	endmenu