Modules | |
| INVOCATION MECHANISMS | |
| This section describes the invocation mechanisms, for the APIs mentioned in this document. | |
| APIs CLASSIFICATION | |
| This section enlists the classification of SCTP APIS. | |
| SERVICE USER APIS - FUNCTIONAL INTERFACE | |
| This section enlists the Service User (SU) API's required with Functional Interface. | |
| SYSTEM MANAGEMENT APIS - FUNCTIONAL INTERFACE | |
| This section enlists information about System Management (SM) APIs. | |
| SERVICE USER APIS - MESSAGE BASED INTERFACE | |
| This section details the Service User(SU) APIs for Messaged Based Interface. | |
| SYSTEM MANAGEMENT APIS - MESSAGE-BASED INTERFACE | |
| This section describes and lists System Management APIs for Message-Based Interface. | |
| TRANSPORT LAYER APIS | |
| This section lists and describes Transport Layer APIs. | |
The APIs provide the application developer with a method to access the functionality of the stack and use its services. The Application passes appropriate parameters to the AP, through the structures defined for each API. The following chapters explain API Usage in detail, and the parameters required for invocation of each API.
APIs are categorized as:
APIs are provided for the following primitives (as listed in RFC 2960): INITIALIZE, ASSOCIATE, SHUTDOWN, ABORT, SEND, SETPRIMARY, RECEIVE, STATUS, CHANGEHEARTBEAT, REQUESTHEARTBEAT, GETSRTTREPORT, SETFAILURETHRESHOLD, and SETPROTOCOLPARAMETERS, RECEIVE_UNSENT, RECEIVE_UNACKED, FLUSH BUFFERS. The APIs for these are discussed in Service User APIs - Functional Interface Section.
1.2.18