Manpage of N_CONN_REQ

N_CONN_REQ

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

NAME

N_CONN_REQ, N_conn_req_t - network connection request

SYNOPSIS

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

typedef struct {
    ulong PRIM_type;    /* always N_CONN_REQ */
    ulong DEST_length;  /* destination address length */
    ulong DEST_offset;  /* destination address offset */
    ulong CONN_flags;   /* bit masking for options flags */
    ulong QOS_length;   /* QOS parameters' length */
    ulong QOS_offset;   /* QOS parameters' offset */
} N_conn_req_t;
/* Flags to indicate if options are requested */
#define REC_CONF_OPT    0x00000001L
#define EX_DATA_OPT     0x00000002L

DESCRIPTION

This primitive requests that the NS provider make a network connection to the specified destination.

The specification of the 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 (see N_INFO_ACK(7)). If the user does not specify QOS parameter values, the default values (specified via N_OPTMGMT_REQ(7)) are used by the NS provider.

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. This field will accommodate variable length addresses within a range supported by the NS provider.

DEST_offset

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

CONN_flags

Specifies the connection flags that are a bitwise OR of any of the following flags:

REC_CONF_OPT: The receipt confirmation selection parameter indicates the use/availability of the receipt confirmation service on the NC. The receipt confirmation service must be supported by the NS provider to be used on the NC.
EX_DATA_OPT: Indicates the use 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 apply to the NC being requested. If the NS user cannot determine the value of a QOS parameter, its value should 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 beginning of the M_PROTO(9) message block.

STATE

This primitive is valid in state NS_IDLE.

NEW STATE

The new state is NS_WCON_CREQ.

RESPONSE

The following acknowledgments are valid for this primitive:

Successful NC Establishment:
This is indicated via the N_CONN_CON(7) primitive. This results in the data transfer state.
Unsuccessful NC Establishment:
This is indicated via the N_DISCON_IND(7) primitive. For example, a connection may be rejected because either the called NS user cannot be reached, or the NS provider and/or the called NS user did not agree with the specified QOS. This results in the idle state.
Non-fatal errors:
These are indicated via the N_ERROR_ACK(7) primitive.

ERRORS

The applicable non-fatal errors are defined as follows:

[NACCESS]: The user did not have proper permissions for the use of the requested address or options.
[NBADQOSPARAM]: The QOS parameter values specified are outside the range supported by the NS provider.
[NBADQOSTYPE]: The QOS structure type is not supported by the NS provider.
[NBADADDR]: The network address was in an incorrect format or contained illegal information. It is not intended to indicate NC errors, such as an unreachable destination. These errors types are indicated via the N_DISCON_IND(7) primitive.
[NBADOPT]: The options were in an incorrect format, or they contained illegal information.
[NOUTSTATE]: The primitive was issued from an invalid state.
[NBADDATA]: The amount of user data specified was outside the range supported by the NS provider.
[NSYSERR]: A system error has occurred and the Linux system error is indicated in the primitive.

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: 23:19:20 GMT, May 21, 2013