T_BIND_ACK

Section: Transport Provider Interface (TPI) (7)
Updated: 2008-10-31
Index Return to Main Contents

NAME

T_BIND_ACK - Bind Protocol Address Acknowledgment

SYNOPSIS

This message consists of one M_PCPROTO message block formatted as follows:

struct T_bind_ack {
    t_scalar_t    PRIM_type;      /* Always T_BIND_ACK */
    t_scalar_t    ADDR_length;
    t_scalar_t    ADDR_offset;
    t_uscalar_t   CONIND_number;
};

DESCRIPTION

This primitive indicates to the transport user that the specified protocol address has been bound to the stream, that the specified number of connect indications are allowed to be queued by the transport provider for the specified protocol address, and that the stream associated with the specified protocol address has been activated.

PARAMETERS

PRIM_type: indicates the primitive type.
ADDR_length: is the length of the protocol address that was bound to the stream.
ADDR_offset: is the offset from the beginning of the M_PCPROTO block where the protocol address begins.
CONIND_number: is the accepted number of connect indications allowed to be outstanding by the transport provider for the specified protocol address. Note that this field does not apply to connectionless transport providers.

The proper alignment of the address in the M_PCPROTO message block is not guaranteed.

RULES

The following rules apply to the binding of the specified protocol address to the stream:

-: If the ADDR_length field in the T_BIND_REQ(7) primitive is 0, then the transport provider is to assign a transport protocol address to the user.
-: The transport provider is to bind the transport protocol address as specified in the T_BIND_REQ(7) primitive.
-: If the transport provider cannot bind the specified address the provider will return [TADDRBUSY].

The following rules apply to negotiating the CONIND_number argument:

-: The returned value must be less than or equal to the corresponding requested number as indicated in the T_BIND_REQ(7) primitive.
-: If the requested value is greater than zero, the returned value must also be greater than zero.
-: Only one stream that is bound to the indicated protocol address may have a negotiated accepted number of maximum connect requests greater than zero.
-: If a stream with CONIND_number greater than zero is used to accept a connection, the stream will be found busy during the duration of that connection and no other stream may be bound to that protocol address with a CONIND_number greater than zero. This will prevent more than one stream bound to the identical protocol address from accepting connect indications.
-: A stream requesting a CONIND_number of zero should always be valid. This indicates to the transport provider that the stream is to be used to request connections only.
-: A stream with a negotiated CONIND_number greater than zero may generate connect requests or accept connect indications.

ERRORS

If the above rules result in an error condition, then the transport provider must issue an T_ERROR_ACK(7) primitive to the transport user specifying the error as defined in the description of the T_BIND_REQ(7) primitive.

MODES

Both connection-mode and connectionless-mode.

ORIGINATOR

Transport provider.

HISTORY

The Transport Provider Interface first appeared in SVR 4[1].

CONFORMANCE

This interface conforms to TPI Version 2, Draft 2[2].

REFERENCES

[1]: SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[2]: TPI Revision 2.0.0, Open Group CAE Specification: Transport Provider Interface (TPI) Specification, Revision 2.0.0, Draft 2, 1999, (Berkshire, UK), OpenGroup, Open Group Publication. <http://www.opengroup.org/onlinepubs/>
[3]: Magic Garden, The Magic Garden Explained: The Internals of UNIX® System V Release 4 / An Open Systems Design, 1994, (Australia), B. Goodheart, J. Cox, Prentice Hall. [ISBN 0-13-098138-9]
[4]: Advanced Programming in the UNIX®Environment, 15th edition, December 1997, (Reading, Massachusetts), W. R. Stevens, Addison Wesley. [ISBN 0-201-56317-7]

TRADEMARKS

OpenSS7tm: is a trademark of OpenSS7 Corporation.
Linux®: is a registered trademark of Linus Torvalds.
UNIX®: is a registered trademark of The Open Group.
Solaris®: is a registered trademark of Sun Microsystems.

Other trademarks are the property of their respective owners.

IDENTIFICATION

OpenSS7 XTI/TLI Networking: Package strxnet version 0.9.2.12 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 09:06:35 GMT, September 09, 2010

Description: Manual Page

Keywords: ss7 ss7/ip ss7 over ip ss7 mtp ss7 sccp ss7 tcap sigtran mtp sccp tcap openss7 acb56 linux telephony pstn linux telephony linux nebs linux compactpci