This struct contains some parameters that may be set or got with the sctp_getInstanceParams()/sctp_setInstanceParams() functions.
-
unsigned int rtoMin
- the minimum timeout value
-
unsigned int validCookieLife
- the lifetime of a cookie
-
unsigned int assocMaxRetransmits
- maximum retransmissions per association
-
unsigned int pathMaxRetransmits
- maximum retransmissions per path
-
unsigned int maxInitRetransmits
- maximum initial retransmissions
-
unsigned int myRwnd
- from recvcontrol : my receiver window
-
unsigned int delay
- recvcontrol: delay for delayed ACK in msecs
-
unsigned char ipTos
- per instance: for the IP type of service field.
-
unsigned int maxSendQueue
- currently unused, will limit the number of chunks queued in the send queue later
-
unsigned int maxRecvQueue
- currently unused, may limit the number of chunks queued in the receive queue later.
Documentation
This struct contains some parameters that may be set or
got with the sctp_getInstanceParams()/sctp_setInstanceParams()
functions. So these may also be specified/retrieved for
servers, before an association is established !
unsigned int rtoMin
- the minimum timeout value
unsigned int validCookieLife
- the lifetime of a cookie
unsigned int assocMaxRetransmits
- maximum retransmissions per association
unsigned int pathMaxRetransmits
- maximum retransmissions per path
unsigned int maxInitRetransmits
- maximum initial retransmissions
unsigned int myRwnd
- from recvcontrol : my receiver window
unsigned int delay
- recvcontrol: delay for delayed ACK in msecs
unsigned char ipTos
- per instance: for the IP type of service field.
unsigned int maxSendQueue
- currently unused, will limit the number of chunks queued in the send queue later
unsigned int maxRecvQueue
- currently unused, may limit the number of chunks queued in the receive queue later.
Is this really needed ? The protocol limits the receive queue with
window advertisement of arwnd==0
Alphabetic index HTML hierarchy of classes or Java
This page was generated with the help of DOC++.