| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | menu "DCCP CCIDs Configuration" |
|---|
| 2 | 3 | |
|---|
| 3 | 4 | config IP_DCCP_CCID2_DEBUG |
|---|
| 4 | 5 | bool "CCID-2 debugging messages" |
|---|
| 5 | | - ---help--- |
|---|
| 6 | + help |
|---|
| 6 | 7 | Enable CCID-2 specific debugging messages. |
|---|
| 7 | 8 | |
|---|
| 8 | 9 | The debugging output can additionally be toggled by setting the |
|---|
| .. | .. |
|---|
| 13 | 14 | config IP_DCCP_CCID3 |
|---|
| 14 | 15 | bool "CCID-3 (TCP-Friendly)" |
|---|
| 15 | 16 | def_bool y if (IP_DCCP = y || IP_DCCP = m) |
|---|
| 16 | | - ---help--- |
|---|
| 17 | + help |
|---|
| 17 | 18 | CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based |
|---|
| 18 | 19 | rate-controlled congestion control mechanism. TFRC is designed to |
|---|
| 19 | 20 | be reasonably fair when competing for bandwidth with TCP-like flows, |
|---|
| .. | .. |
|---|
| 25 | 26 | relatively smooth sending rate is of importance. |
|---|
| 26 | 27 | |
|---|
| 27 | 28 | CCID-3 is further described in RFC 4342, |
|---|
| 28 | | - http://www.ietf.org/rfc/rfc4342.txt |
|---|
| 29 | + https://www.ietf.org/rfc/rfc4342.txt |
|---|
| 29 | 30 | |
|---|
| 30 | 31 | The TFRC congestion control algorithms were initially described in |
|---|
| 31 | 32 | RFC 5348. |
|---|
| 32 | 33 | |
|---|
| 33 | 34 | This text was extracted from RFC 4340 (sec. 10.2), |
|---|
| 34 | | - http://www.ietf.org/rfc/rfc4340.txt |
|---|
| 35 | + https://www.ietf.org/rfc/rfc4340.txt |
|---|
| 35 | 36 | |
|---|
| 36 | 37 | If in doubt, say N. |
|---|
| 37 | 38 | |
|---|
| 38 | 39 | config IP_DCCP_CCID3_DEBUG |
|---|
| 39 | 40 | bool "CCID-3 debugging messages" |
|---|
| 40 | 41 | depends on IP_DCCP_CCID3 |
|---|
| 41 | | - ---help--- |
|---|
| 42 | + help |
|---|
| 42 | 43 | Enable CCID-3 specific debugging messages. |
|---|
| 43 | 44 | |
|---|
| 44 | 45 | The debugging output can additionally be toggled by setting the |
|---|