Based on the taxonomy defined for Windows Sockets 2 protocol-independent multipoint/multicast schemes, ATM falls into the category of "rooted data" and "rooted control" planes. (See Windows Sockets 2 API specification, Appendix D for more information.) An application acting as the root would create c_root sockets and counterparts running on leaf nodes would utilize c_leaf sockets. The root application will use WSAJoinLeaf to add new leaf nodes. The corresponding applications on the leaf nodes will have set their c_leaf sockets into the listening mode. WSAJoinLeaf with a c_root socket specified will be mapped to the Q.2931 SETUP message (for the first leaf) or ADD PARTY message (for any subsequent leaves).
Note The QOS parameters specified in WSAJoinLeaf for any subsequent leaves should be ignored per the ATM Forum UNI specification.
The leaf-initiated join is not part of the ATM UNI 3.1, but will be supported in the ATM UNI 4.0. Thus WSAJoinLeaf with a c_leaf socket specified will be mapped to the appropriate ATM UNI 4.0 message.
The AAL Parameter and B-LLI negotiation is supported via the modification of the corresponding IEs in the lpSQOS parameter upon the invocation of the condition function specified in WSAAccept.
Note Only certain fields in those two IEs can be modified. See the ATM Forum UNI specification Appendix C and F for details.