Manpage of N_BIND_REQ

N_BIND_REQ

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

NAME

N_BIND_REQ, N_bind_req_t - Bind Protocol Address Request

SYNOPSIS

The format of the message is one M_PROTO(9) message block and its structure is as follows:

typedef struct {
    ulong PRIM_type;       /* always N_BIND_REQ */
    ulong ADDR_length;     /* length of address */
    ulong ADDR_offset;     /* offset of address */
    ulong CONIND_number;   /* req # of conn-indications to be queued */
    ulong BIND_flags;      /* flags associated with N_BIND_REQ */
    ulong PROTOID_length;  /* length of the protocol id */
    ulong PROTOID_offset;  /* offset of protocol id */
} N_bind_req_t;
/* Flags associated with N_BIND_REQ */
#define DEFAULT_LISTENER  0x00000001L
#define TOKEN_REQUEST     0x00000002L
#define DEFAULT_DEST      0x00000004L

DESCRIPTION

This primitive requests that the NS provider bind a NS user entity to a network address and negotiate the number of connect indications allowed to be outstanding by the NS provider for the specified NS user entity being bound.

PARAMETERS

PRIM_type

Is the primitive type.

ADDR_length

Is the length in bytes of the network address to be bound to the stream.

ADDR_offset

Is the offset from the beginning of the M_PROTO(9) where the network address begins.

CONIND_number

Is the requested number of connect indications allowed to be outstanding by the NS provider for the specified protocol address. (If the number of outstanding connect indications equals CONIND_number, the NS provider need not discard further incoming connect indications, but may choose to queue them internally until the number of outstanding connect indications drops below the CONIND_number.) Only one stream per network address is allowed to have a CONIND_number value greater than zero. This indicates to the network provider that this stream is the listener stream for the NS user. This stream will be used by the NS provider for connect indications for that network address. If a stream is bound as a listener stream, it will not be able to initiate connect requests. If the NS user attempts to send an N_CONN_REQ(7) primitive down this stream, an N_ERROR_ACK(7) message will be sent to the NS user by the NS provider with an error value fo NACCESS. This field should be ignored in CLNS.

BIND_flags

Bind flags-any of the following flags:

DEFAULT_LISTENER

When set, this flag indicates that this stream is the "default listener stream". This stream is used to pass connect indications for all incoming calls that contain protocol identifiers that are not bound to any other listener, or when a listener stream with CONIND_number value of greater than zero is not found. Also, the default listener will receive all incoming call indications that contain no user data.

Only one default listener stream is allowed per occurrence of NPI. An attempt to bind a default listener stream when one is already bound should result in an error (of type NBOUND).

The DEFAULT_LISTENER flag is ignored in CLNS.

TOKEN_REQUEST

When set, this flag indicates to the NS provider that the NS user has requested that a "token" be assigned to the stream (to be used in the NC response message), and the token value be returned to the NS user via the N_BIND_ACK(7) primitive. The token assigned by the NS provider can then be used by the NS user in a subsequent N_CONN_RES(7) primitive to identify the stream on which the NC is to be established. The TOKEN_REQUEST flag is ignored in CLNS.

DEFAULT_DEST

When set, this flag indicates that this stream is the "default destination stream." This stream will receive all packets destined for the NSAP specified in the bind request. If no NSAP is indicated in the bind request, then this stream should receive all packets destined to an NSAP which is bound to no other stream. Only one default destination stream per NSAP is allowed per occurrence of NPI. An attempt to bind a default destination stream to an NSAP when one is already bound should result in an error of type NBOUND.

The DEFAULT_DEST flag is ignored in the CONS.

PROTOID_length

Is the length in bytes of the protocol ids to be bound to the stream.

PROTOID_offset

Is the offset from the beginning of the M_PROTO(9) block where the protocol id begins.

STATE

This primitive is valid in state NS_UNBND (see Appendix B).

NEW STATE

The new state is NE_WACK_BREQ.

RESPONSE

The NS provider will generate one of the following acknowledgments upon receipt ofthe N_BIND_REQ(7) primitive:

Successful:
Correct acknowledgment of the primitive is indicated via the N_BIND_ACK(7) primitive.
Non-fatal errors:
These errors will be indicated via the N_ERROR_ACK(7) primitive. The applicable non-fatal errors are as follows:

ERRORS

[NBADADDR]: The network address was in an incorrect format or the address contained illegal information. It is not intended to indicate protocol errors.
[NBOUND]: The NS user attempted to bind a second stream to a network address with the CONIND_number set to a non-zero value, or attempted to bind a second stream with the DEFAULT_LISTENER flag value set to non-zero.
[NNOADDR]: The NS provider could not allocate an address.
[NACCESS]: The user did not have proper permissions for the use of the requested address.
[NOUTSTATE]: The primitive was issued from an invalid state.
[NSYSERR]: A system error has occurred and the Linux system error is indicated in the primitive.
[NNOPROTOID]: Protocol identifier could not be allocated.

HISTORY

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

CONFORMANCE

This interface conforms to NPI Revision 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]: NPI, Open Group CAE Specification: Network Provider Interface (NPI) Specification, Revision 2.0.0, Draft 2, August 17, 1992, (Parsippany, New Jersey), UNIXInternational,Inc., UNIX International Press. <http://www.openss7.org/docs/npi.pdf>
[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 XNS Networking: Package strxns version 0.9.2.7 released 2008-10-31.

This document was created by man2html, using the manual pages.
Time: 19:02:51 GMT, May 22, 2013