2005-08-10 07:14:34 +04:00
menu "DCCP CCIDs Configuration (EXPERIMENTAL)"
2007-11-21 15:11:52 +03:00
depends on EXPERIMENTAL
2005-08-10 07:14:34 +04:00
2006-09-20 00:12:44 +04:00
config IP_DCCP_CCID2_DEBUG
2009-01-05 08:42:53 +03:00
bool "CCID-2 debugging messages"
---help---
Enable CCID-2 specific debugging messages.
2006-11-20 23:26:03 +03:00
2009-01-05 08:42:53 +03:00
The debugging output can additionally be toggled by setting the
ccid2_debug parameter to 0 or 1.
2006-09-20 00:12:44 +04:00
2009-01-05 08:42:53 +03:00
If in doubt, say N.
2006-09-20 00:12:44 +04:00
2005-08-10 07:14:34 +04:00
config IP_DCCP_CCID3
2009-01-05 08:42:53 +03:00
bool "CCID-3 (TCP-Friendly) (EXPERIMENTAL)"
def_bool y if (IP_DCCP = y || IP_DCCP = m)
2005-08-10 07:14:34 +04:00
---help---
2009-01-05 08:42:53 +03:00
CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
2005-08-10 07:14:34 +04:00
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
2009-01-05 08:42:53 +03:00
throughput over time compared with TCP, which makes CCID-3 more
suitable than CCID-2 for applications such streaming media where a
2005-08-10 07:14:34 +04:00
relatively smooth sending rate is of importance.
2009-01-05 08:42:53 +03:00
CCID-3 is further described in RFC 4342,
2006-10-25 03:17:51 +04:00
http://www.ietf.org/rfc/rfc4342.txt
2006-03-21 04:41:47 +03:00
The TFRC congestion control algorithms were initially described in
2009-01-11 11:17:22 +03:00
RFC 5348.
2005-08-10 07:14:34 +04:00
2006-10-25 03:17:51 +04:00
This text was extracted from RFC 4340 (sec. 10.2),
http://www.ietf.org/rfc/rfc4340.txt
2006-11-20 23:26:03 +03:00
2009-01-05 08:42:53 +03:00
If in doubt, say N.
2005-08-10 07:14:34 +04:00
2006-11-20 23:28:09 +03:00
config IP_DCCP_CCID3_DEBUG
2009-01-05 08:42:53 +03:00
bool "CCID-3 debugging messages"
depends on IP_DCCP_CCID3
---help---
Enable CCID-3 specific debugging messages.
2006-11-20 23:28:09 +03:00
2009-01-05 08:42:53 +03:00
The debugging output can additionally be toggled by setting the
ccid3_debug parameter to 0 or 1.
2006-11-20 23:28:09 +03:00
2009-01-05 08:42:53 +03:00
If in doubt, say N.
2006-12-03 19:50:23 +03:00
2007-12-06 17:26:38 +03:00
config IP_DCCP_TFRC_LIB
2009-01-05 08:45:33 +03:00
def_bool y if IP_DCCP_CCID3
2007-12-06 17:26:38 +03:00
config IP_DCCP_TFRC_DEBUG
2009-01-05 08:45:33 +03:00
def_bool y if IP_DCCP_CCID3_DEBUG
2005-08-10 07:14:34 +04:00
endmenu