tpi_sctp.7.man

This a separate release of the OpenSS7 X/Open XTI/TLI library, TLI modules (timod, tirdwr) and the I

.IR REMADDR_length " and " REMADDR_offset
return zero (0).
.SS T_CAPABILITY_REQ
.PP
.PP
This primitive is interpreted as in
.BR tpi (7).
.SS T_CAPABILITY_ACK
.PP
.PP
This primitive returns the
.BR T_info_ack (7)
structure interpreted as described in
.IR \*(lqT_INFO_ACK\*(rq ,
above.
.SS T_BIND_REQ
.PP
.PP
This primitive is interpreted as in
.BR tpi (7).
.TP
.IR ADDR_length ", " ADDR_offset
The length and offset from the beginning of the message block of the
.B sockaddr_in
structures that contain the
.B SCTP
addresses to bind.
.B SCTP
supports wildcard addresses and the address
.BR INADDR_ANY .
This field can contain an integer number of addresses.
.TP
.I CONNIND_number
Specifies the number of connection indications.
.SS T_BIND_ACK
.PP
.PP
This primitive is interpreted as in
.BR tpi (7).
.TP
.IR ADDR_length ", " ADDR_offset
Indicates the length and offset from the beginning of the message block of the
.B sockaddr_in
structures that contain the
.B SCTP
addresses that were bound.
This field can contain an integer number of addresses.
.TP
.I CONNIND_number
Indicates the number of connection indications.
.SS T_UNBIND_REQ
.PP
.PP
This primitive is interpreted as in
.BR tpi (7).
.SS T_OK_ACK
.PP
.PP
This primitive is interpreted as in
.BR tpi (7).
.SS T_ERROR_ACK
.PP
.PP
This primitive is interpreted as in
.BR tpi (7).
.SS T_OPTMGMT_REQ
.PP
.PP
This primitive is interpreted as in
.BR tpi (7),
with the options described under
.IR \*(lqOPTIONS\*(rq ,
above.
.SS T_OPTMGMT_ACK
.PP
.PP
This primitive is interpreted as in
.BR tpi (7),
with the options described under
.IR \*(lqOPTIONS\*(rq ,
above.
.SH "PROTOCOL SERVICE INTERFACE"
.PP
.PP
.SS T_UNITDATA_REQ
.PP
.PP
.B SCTP
does not support connectionless service.  The
.B SCTP
transport service provider will return
.RB [ TNOTSUPP ]
in the
.I TLI_error
field of the
.BR T_ERROR_ACK (7)
primitive.
.SS T_UNITDATA_IND
.PP
.PP
.B SCTP
does not support connectionless service.  The
.B SCTP
transport service provider will never issue this primitive.
.SS T_UDERROR_IND
.PP
.PP
.B SCTP
does not support connectionless service.  The
.B SCTP
transport service provider will never issue this primitive.
.SS T_CONN_REQ
.PP
.PP
This primitive is interpreted as in
.BR tpi (7),
with the options described under
.IR \*(lqOPTIONS\*(rq ,
above and the following considerations:
.TP
.IR DEST_length ", " DEST_offset
Specifies the length and offset from the beginning of the message block of the
.B sockaddr_in
structures that contains the
.B SCTP
addresses to which to connect the stream.
For connection to multi-homed
.B SCTP
hosts, this address may contain multiple
.B sockaddr_in
structures.
.TP
.IR OPT_length ", " OPT_offset
Specifies the length and offset from the beginning of the message block of the
options containing the connection options to use when forming an association
with the peer.  These option values can be changed with the
.BR T_OPTMGMT_REQ (7)
primitive, or overridden for a specific message with the
.BR T_OPTDATA_REQ (7)
primitive.
.sp
Options that have end-to-end significance are:
.BR T_SCTP_OSTREAMS " and " T_SCTP_ISTREAMS .
.sp
Options that have significance at connection are:
.BR T_SCTP_SACK_DELAY ,
.BR T_SCTP_PATH_MAX_RETRANS ,
.BR T_SCTP_ASSOC_MAX_RETRANS ,
.BR T_SCTP_MAX_INIT_RETRIES ,
.BR T_SCTP_HEARTBEAT_ITVL ,
.BR T_SCTP_RTO_INITIAL ,
.BR T_SCTP_RTO_MIN " and "
.BR T_SCTP_RTO_MAX .
.SS T_CONN_CON
.PP
.PP
This primitive is interpreted as in
.BR tpi (7),
with the options described under
.IR \*(lqOPTIONS\*(rq ,
above and the following considerations:
.TP
.IR RES_length ", " RES_offset
Indicates the length and offset from the beginning of the message block of the
.B sockaddr_in
structures that contains the
.B SCTP
addresses to which the stream is confirmed connected.
For responding multi-homed
.B SCTP
hosts, this address may contain multiple
.B sockaddr_in
structures.
.TP
.IR OPT_length ", " OPT_offset
.SS T_CONN_IND
.PP
.PP
This primitive is interpreted as in
.BR tpi (7),
with the options described under
.IR \*(lqOPTIONS\*(rq ,
above and the following considerations:
.TP
.IR SRC_length ", " SRC_offset
Indicates the length and offset from the beginning of the message block of the
.B sockaddr_in
structures that contains the
.B SCTP
addresses from which the remote
.B SCTP
is connecting.
For connecting multi-homed
.B SCTP
hosts, this address may contain multiple
.B sockaddr_in
structures.
.TP
.IR OPT_length ", " OPT_offset
.SS T_CONN_RES
.PP
.PP
This primitive is interpreted as in
.BR tpi (7),
with the options described under
.IR \*(lqOPTIONS\*(rq ,
above and the following considerations:
.TP
.IR OPT_length ", " OPT_offset
.SS T_DATA_REQ
.PP
.PP
Data will be sent ordered on the stream.
.SS T_DATA_IND
.PP
.PP
Data was sent ordered on the stream.
.SS T_EXDATA_REQ
.PP
.PP
Data will be sent unordered on the stream.
.SS T_EXDATA_IND
.PP
.PP
Data was sent unordered on the stream.
.SS T_OPTDATA_REQ
.PP
.PP
.TP
.I DATA_flag
This field can contain a bitwise OR of the following flags:
.RS
.TP
.B T_ODF_MORE
Specifies that the next
.BR T_OPTDATA_REQ (7)
primitive contains data belonging to the same TSDU.
.TP
.B T_ODF_EX
Specifies that the data is expedited.
.B SCTP
does not support true expedited data.  Data will be sent unordered within the
association.
.RE
.TP
.IR OPT_length ", " OPT_offset
Specifies the length and offset from the beginning of the message block of
options associated with the data.
Options that are significant are:
.BR T_SCTP_CORK ,
.BR T_SCTP_PPI  " and "
.BR T_SCTP_SID .
.B T_SCTP_CORK
specifies that data should be held from transmission until subsequent data is
sent.
.B T_SCTP_PPI
specifies the Protocol Payload Identifier to associate with the data.
.B T_SCTP_SID
specifies the
.B SCTP
stream within the association upon which to send the data.
.SS T_OPTDATA_IND
.PP
.PP
.TP
.I DATA_flag
This field can contain a bitwise OR of the following flags:
.RS
.TP
.B T_ODF_MORE
Indicates that the next
.BR T_OPTDATA_REQ (7)
primitive contains data belonging to the same TSDU.
.TP
.B T_ODF_EX
Indicates that the data is expedited.
.B SCTP
does not support true expedited data.  Data was received unordered within the
association.
.RE
.TP
.IR OPT_length ", " OPT_offset
Options that are significant are:
.BR T_SCTP_PPI ,
.BR T_SCTP_SID ,
.BR T_SCTP_SSN " and "
.BR T_SCTP_TSN .
.B T_SCTP_PPI
indicates the Protocol Payload Identifier associated with the data.
.B T_SCTP_SID
indicates the stream identifier of the
.B SCTP
stream within the association upon which the data was received.
.B T_SCTP_SSN
indicates the stream sequence number for the current data chunk.
.B T_SCTP_TSN
indicates the transmission sequence number for the current data chunk.
.SS T_DISCON_REQ
.PP
.PP
This primitive is interpreted as specified in
.BR tpi (7).
This will result in the refusal of an outstanding
.B SCTP
connection indication or an abortive release of an existing
.B SCTP 
association.
.SS T_DISCON_IND
.PP
.PP
This primitive is interpreted as specified in
.BR tpi (7).
It indicates the refusal of an outstanding
.B SCTP
outgoing connection request, or the abortive release of an existing
.B SCTP
association.
.TP
.I DISCON_reason
The disconnect reason may be one of the following values:
.RS
.RE
.SS T_ORDREL_REQ
.PP
.PP
This primitive is interpreted as specified in
.BR tpi (7).
This primitive initiates or responds to an
.B SCTP
orderly release.
.SS T_ORDREL_IND
.PP
.PP
This primitive is interpreted as specified in
.BR tpi (7).
This primitive indicates or confirms an
.B SCTP
orderly release.
.SH "IOCTLS"
.PP
.PP
.SH "ERROR HANDLING"
.PP
.PP
.SH "ERRORS"
.PP
.PP
.SH "CAVEATS"
.PP
.PP
.SH "SEE ALSO"
.PP
.BR sctp (7),
.BR tpi (7),
.BR xti (3),
.BR sockets (3).
.SH "VERSIONS"
.PP
.PP
This manpage describes Version 5.2 of the
.B TPI-SCTP
interface.
.XX
.[
TPI Revision 2.0.0
.]
.[
rfc2960
.]
.[
rfc3309
.]
.[
sctp-mib
.]
.[
prsctp
.]
.[
addip
.]
.[
sctpig
.]
.[
$LIST$
.]
.TA