Manpage of N_CONN_IND

N_CONN_IND

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

NAME

N_CONN_IND, N_conn_ind_t - network connection indication

SYNOPSIS

The format of this message is one M_PROTO(9) message block followed by one or more M_DATA(9) blocks for NS user data. The structure of the M_PROTO(9) message block is as follows:

typedef struct {
    ulong PRIM_type;    /* always N_CONN_IND */
    ulong DEST_length;  /* destination address length */
    ulong DEST_offset;  /* destination address offset */
    ulong SRC_length;   /* source address length */
    ulong SRC_offset;   /* source address offset */
    ulong SEQ_number;   /* sequence number */
    ulong CONN_flags;   /* bit masking for options flags */
    ulong QOS_length;   /* QOS parameters' length */
    ulong QOS_offset;   /* QOS parameters' offset */
} N_conn_ind_t;

DESCRIPTION

This primitive indicates to the destination NS user that a network connect request has been made by the user at the specified source address.

The specification of NS user data is optional. The NS user can send any integral number of octets of data within the range supported by the NS provider. The NS user data will only be present if the corresponding N_CONN_REQ(7) had NS user data parameter specified, and their data will be identical.

PARAMETERS

PRIM_type

Indicates the primitive type.

DEST_length

Indicates the length of the destination address parameter that conveys an address identifying the NS user to which the NC is to be established.

DEST_offset

Is the offset of the destination address from the beginning of the M_PROTO(9) message block.

SRC_length

The source address parameter conveys the network address ofthe NS user from which the NC has been requested. The semantics of the value in the N_CONN_IND primitive isidentical to the value associated with the stream on which the N_CONN_REQ(7) was issued.

SRC_offset

Is the offset of the destination address from the beginning of the M_PROTO(9) message block.

SEQ_number

Identifies the sequence number that can be used by the NS userto associate this message with the N_CONN_RES(7) or N_DISCON_REQ(7) primitive that is to follow. This value must be unique among the outstanding N_CONN_IND messages. The use of this field allows the NS user to issue the N_CONN_RES(7) or the N_DISCON_REQ(7) messages in any order.

CONN_flags

Indicates the connection flags that can be a bitwise OR of any of the following values:

REC_CONF_OPT: The receipt confirmation selection parameter indicates the use/availability of the receipt confirmation service on the NC. The receiptconfirmation service must be provided in the network service to be used on the NC.
EX_DATA_OPT: The expedited data selection parameter indicates the use/availability of the expedited data transfer service on the NC. The expedited data transfer service must be provided by the NS provider for it to be used on the NC.

QOS_length

Indicates the length of the QOS parameters values that are negotiated during NC establishment. If the destination NS user does not agree to the range of QOS values specified by the source NS user in the N_CONN_REQ(7) primitive, it will reject the NC establishment by invoking a N_DISCON_REQ(7) primitive (the originator parameter in the N_DISCON_REQ(7) primitive will indicate NS user initiated release). If the NS user does not support or cannot determine the value of a QOS parameter, its value will be set to QOS_UNKNOWN. If the NS user does not specify any QOS parameter values, the length of this field should be set to zero.

QOS_offset

Indicates the offset of the QOS parameters from the beginningof the M_PROTO(9) message block.

STATE

This primitive is valid in the states NS_IDLE and NS_WRES_CIND.

NEW STATE

In both cases the resulting state is NS_WRES_CIND (the number of connect indications waiting for user response is incremented by one).

CONFORMANCE

This interface conforms to NPI Revision 2[1].

HISTORY

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

REFERENCES

[1]: 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>
[2]: SVR 4, UNIX® System V Release 4 Programmer's Manual, 1990, (Englewood Cliffs, New Jersey), AT&T UNIX System Laboratories, Inc., Prentice Hall.
[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: 09:52:19 GMT, May 24, 2013