dccp.txt 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131
  1. DCCP protocol
  2. ============
  3. Contents
  4. ========
  5. - Introduction
  6. - Missing features
  7. - Socket options
  8. - Notes
  9. Introduction
  10. ============
  11. Datagram Congestion Control Protocol (DCCP) is an unreliable, connection
  12. based protocol designed to solve issues present in UDP and TCP particularly
  13. for real time and multimedia traffic.
  14. It has a base protocol and pluggable congestion control IDs (CCIDs).
  15. It is at proposed standard RFC status and the homepage for DCCP as a protocol
  16. is at:
  17. http://www.read.cs.ucla.edu/dccp/
  18. Missing features
  19. ================
  20. The DCCP implementation does not currently have all the features that are in
  21. the RFC.
  22. The known bugs are at:
  23. http://linux-net.osdl.org/index.php/TODO#DCCP
  24. Socket options
  25. ==============
  26. DCCP_SOCKOPT_SERVICE sets the service. The specification mandates use of
  27. service codes (RFC 4340, sec. 8.1.2); if this socket option is not set,
  28. the socket will fall back to 0 (which means that no meaningful service code
  29. is present). On active sockets this is set before connect(); specifying more
  30. than one code has no effect (all subsequent service codes are ignored). The
  31. case is different for passive sockets, where multiple service codes (up to 32)
  32. can be set before calling bind().
  33. DCCP_SOCKOPT_GET_CUR_MPS is read-only and retrieves the current maximum packet
  34. size (application payload size) in bytes, see RFC 4340, section 14.
  35. DCCP_SOCKOPT_SEND_CSCOV and DCCP_SOCKOPT_RECV_CSCOV are used for setting the
  36. partial checksum coverage (RFC 4340, sec. 9.2). The default is that checksums
  37. always cover the entire packet and that only fully covered application data is
  38. accepted by the receiver. Hence, when using this feature on the sender, it must
  39. be enabled at the receiver, too with suitable choice of CsCov.
  40. DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
  41. range 0..15 are acceptable. The default setting is 0 (full coverage),
  42. values between 1..15 indicate partial coverage.
  43. DCCP_SOCKOPT_RECV_CSCOV is for the receiver and has a different meaning: it
  44. sets a threshold, where again values 0..15 are acceptable. The default
  45. of 0 means that all packets with a partial coverage will be discarded.
  46. Values in the range 1..15 indicate that packets with minimally such a
  47. coverage value are also acceptable. The higher the number, the more
  48. restrictive this setting (see [RFC 4340, sec. 9.2.1]). Partial coverage
  49. settings are inherited to the child socket after accept().
  50. The following two options apply to CCID 3 exclusively and are getsockopt()-only.
  51. In either case, a TFRC info struct (defined in <linux/tfrc.h>) is returned.
  52. DCCP_SOCKOPT_CCID_RX_INFO
  53. Returns a `struct tfrc_rx_info' in optval; the buffer for optval and
  54. optlen must be set to at least sizeof(struct tfrc_rx_info).
  55. DCCP_SOCKOPT_CCID_TX_INFO
  56. Returns a `struct tfrc_tx_info' in optval; the buffer for optval and
  57. optlen must be set to at least sizeof(struct tfrc_tx_info).
  58. Sysctl variables
  59. ================
  60. Several DCCP default parameters can be managed by the following sysctls
  61. (sysctl net.dccp.default or /proc/sys/net/dccp/default):
  62. request_retries
  63. The number of active connection initiation retries (the number of
  64. Requests minus one) before timing out. In addition, it also governs
  65. the behaviour of the other, passive side: this variable also sets
  66. the number of times DCCP repeats sending a Response when the initial
  67. handshake does not progress from RESPOND to OPEN (i.e. when no Ack
  68. is received after the initial Request). This value should be greater
  69. than 0, suggested is less than 10. Analogue of tcp_syn_retries.
  70. retries1
  71. How often a DCCP Response is retransmitted until the listening DCCP
  72. side considers its connecting peer dead. Analogue of tcp_retries1.
  73. retries2
  74. The number of times a general DCCP packet is retransmitted. This has
  75. importance for retransmitted acknowledgments and feature negotiation,
  76. data packets are never retransmitted. Analogue of tcp_retries2.
  77. send_ndp = 1
  78. Whether or not to send NDP count options (sec. 7.7.2).
  79. send_ackvec = 1
  80. Whether or not to send Ack Vector options (sec. 11.5).
  81. ack_ratio = 2
  82. The default Ack Ratio (sec. 11.3) to use.
  83. tx_ccid = 2
  84. Default CCID for the sender-receiver half-connection.
  85. rx_ccid = 2
  86. Default CCID for the receiver-sender half-connection.
  87. seq_window = 100
  88. The initial sequence window (sec. 7.5.2).
  89. tx_qlen = 5
  90. The size of the transmit buffer in packets. A value of 0 corresponds
  91. to an unbounded transmit buffer.
  92. sync_ratelimit = 125 ms
  93. The timeout between subsequent DCCP-Sync packets sent in response to
  94. sequence-invalid packets on the same socket (RFC 4340, 7.5.4). The unit
  95. of this parameter is milliseconds; a value of 0 disables rate-limiting.
  96. Notes
  97. =====
  98. DCCP does not travel through NAT successfully at present on many boxes. This is
  99. because the checksum covers the pseudo-header as per TCP and UDP. Linux NAT
  100. support for DCCP has been added.