aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/dccp.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/networking/dccp.txt')
-rw-r--r--Documentation/networking/dccp.txt16
1 files changed, 16 insertions, 0 deletions
diff --git a/Documentation/networking/dccp.txt b/Documentation/networking/dccp.txt
index 74563b38ffd9..a8142a81038a 100644
--- a/Documentation/networking/dccp.txt
+++ b/Documentation/networking/dccp.txt
@@ -47,6 +47,22 @@ the socket will fall back to 0 (which means that no meaningful service code
47is present). Connecting sockets set at most one service option; for 47is present). Connecting sockets set at most one service option; for
48listening sockets, multiple service codes can be specified. 48listening sockets, multiple service codes can be specified.
49 49
50DCCP_SOCKOPT_SEND_CSCOV and DCCP_SOCKOPT_RECV_CSCOV are used for setting the
51partial checksum coverage (RFC 4340, sec. 9.2). The default is that checksums
52always cover the entire packet and that only fully covered application data is
53accepted by the receiver. Hence, when using this feature on the sender, it must
54be enabled at the receiver, too with suitable choice of CsCov.
55
56DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
57 range 0..15 are acceptable. The default setting is 0 (full coverage),
58 values between 1..15 indicate partial coverage.
59DCCP_SOCKOPT_SEND_CSCOV is for the receiver and has a different meaning: it
60 sets a threshold, where again values 0..15 are acceptable. The default
61 of 0 means that all packets with a partial coverage will be discarded.
62 Values in the range 1..15 indicate that packets with minimally such a
63 coverage value are also acceptable. The higher the number, the more
64 restrictive this setting (see [RFC 4340, sec. 9.2.1]).
65
50Notes 66Notes
51===== 67=====
52 68