2.8. Guidelines for Interface Users

SDLI enables a SDL user to be implemented in a protocol-independent manner such that the SDL user can operate over many SDL providers without changing the SDL user software. SDL user implementors must adhere to the following guidelines, however, to achieve this independence.

The protocol-specific service limits returned in the LMI_INFO_ACK primitive (e.g. lmi_max_sdu) must not be exceeded. The SDL user should access these limits and adhere to them while interacting with the SDL provider.
Protocol-specific PPA identifier formats should be hidden from the SDL user software. Hard-coded addresses and identifiers must be avoided. The SDL user should retrieve the necessary information from some other entity (such as a management entity or higher layer protocol entity) and insert it without inspection into the appropriate primitives.
The SDL user should not be written to a specific style of SDL provider (i.e. style 1 vs. style 2). The LMI_INFO_ACK returns sufficient information to identify which style of provider has been accessed, and the SDL user should perform (or not perform) a LMI_ATTACH_REQ accordingly.
The names of devices should not be hard-coded into user-level programs that access a SDL provider.

2.8. Guidelines for Interface Users

OpenSS7