Manpage of N_CI

N_CI

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

NAME

N_CI - Connect Request or Connect Indication

INTERFACE

Network Layer Interface (NLI)[1], nli(7).

SYNOPSIS

#include <netx25/x25_proto.h>
struct xcallf {
    unsigned char xl_type;
    unsigned char xl_command;
    int conn_id;
    unsigned char CONS_call;
    unsigned char negotiate_qos;
    struct xaddrf calledaddr;
    struct xaddrf callingaddr;
    struct qosformat qos;
};

DESCRIPTION

The Connection Request or Indication message primitive, N_CI, is used by the NS user to request an outgoing connection, or by the NS provider to indicate an incoming connection. The control part of the message consists of one M_PROTO(9) message block, and contains the xcallf structure. The data part of the message consists of zero or one M_DATA(9) message blocks containing the Call User Data (CUD) when supplied.

FORMAT

The Connect Request and Connect Indicaiton use the xcallf structure. The control part of the message consists of one M_PROTO(9) message block containing the xcallf structure. The data part of the message consists of zero or one M_DATA(9) message blocks containing the Call User Data (if any).

MEMBERS

The xcallf structure contains the following members:

xl_type: Always XL_CTL.
xl_command: Always N_CI, for both Connect Requests and Connect Indications.
conn_did: This field is used only for Connect Indications. When an NS user Stream is listening, multiple incoming Connect Indications can be pending. This field indicates the connection identifier for the current Connect Indication for use by the NS user when responding to this Connect Indication with either a Connect Response or a Disconnect Request message.
CONS_call: Either X.25[2, 3] or CONS[4] procedures can be used for calls. When non-zero, this field indicates that CONS[4] procedures are to be used. When zero, this field indicates that X.25[2, 3] procedures are to be used.
negotiate_qos: QoS parameters can be negotiated by the peer or left at default values. WHen non-zero, this field specifies or indicates that QoS parameter are being negotiated by the NS user or NS user peer and the pertinent ranges are provided in the qos member. When zero, this field specifies and indicates that default values are ot be used for the NS user or were indicated by the NS user peer.
calledaddr: Conveys the called address. For outgoing Connect Requests, this is the remote address to which the call is to be connected. For incoming Connect Indications, this is the local address to which the call was intitiated.
callingaddr: Conveys the calling address. For outgoing Connect Requests, this is the local address from which the call is to be connected. For incoming Connect Indications, this is the remote address form which the call was initiated.
qos: Conveys the quality of service parameters and CONS or non-CONS facilities that are requested or indicated.

RESPONSE

When the Connect Request is issued by the NS user, the expected response from the NS provider is a Connect Confirmation or a Disconnect Indication.

When the Connect Indication is issued by the NS provider, the expected response from the NS user is a Connect Response or a Disconnect Request.

USAGE

The Connect Request message primitive is equivalent to the N_CONN_REQ(7) primitive of the Network Provider Interface (NPI)[5], npi(7). The Connect Indication is equivalent to the N_CONN_IND(7).

NOTICES

The Network Layer Interface (NLI) is a proprietary interface without a formal standard. Either the Network Provider Interface (NPI)[5], npi(7), or the XTI-X25 interface[6], xti_x25(3), should be used in its stead.

FILES

N_CI is defined in the <netx25/x25_proto.h> file.

COMPATIBILITY

N_CI is compatible with NLI, and implementations based on NLI such as Solaris Solstice® X.25 9.2[7], IRIX SX.25[8], HP-UX X.25/9000, PT X.25[9], with the following considerations:

---: Solaris Solstice® X.25 9.2[7], IRIX SX.25[8], PT X.25[9], are consistent in their documentation of N_CI.
---: NLI is an inherently low level and non-portable interface and should not be used by portable programs. Portable programs should use the NPI or XX25 interfaces in its stead.
---: Binary compatibility is not attempted: only a rough source compatibility. Any binary compatibility exhibited is a bug and is scheduled to be removed in the next release.

See NLI(7), STREAMS(4), for additional compatiblity considerations.

CONFORMANCE

The NLI is not a formal standard. The OpenSS7tm implementation of NLI conforms to documentation for Version 3 of the NLI.

HISTORY

The NLI is an interface originally developed by Spider Systems, Ltd. (now a division of Emmerson Power). The NLI interface found its way into may mainstream UNIX implementations and UNIX-like RTOS sporting STREAMS such as Windriver's VxWorks. The NLI was never standardized and remains an inherently non-portable interface.

VERSIONS

This manual page was written for the OpenSS7tm implementation of X.25.

REFERENCES

[1]: NLI, OpenSS7 CAE Specification: Network Layer Interface (NLI) Specification, Revision 0.9.2, Draft 1, July 15, 2008, (Edmonton, Canada), B. Bidulock, OpenSS7 Corporation. Distributed with package strx25-0.9.2. <http://www.openss7.org/specs/nli.pdf>
[2]: ITU-T Recommendation X.25, Interface between Data Terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to the public data networks by dedicated circuit, October 1996, (Geneva), ITU, ITU-T Telecommunication Standardization Sector of ITU. (Previously "CCITT Recommendation") <http://www.itu.int/rec/T-REC-X.25/>
[3]: ISO/IEC 8208:2000, Information Technology --- Data Communications --- X.25 Packet Layer Protocol For Data Terminal Equipment, Fourth Edition, November 1, 2000, (Geneva), ISO, International Organization for Standardization. <http://www.iso.org/>
[4]: ITU-T Recommendation X.223 [ISO/IEC 8878], Use of X.25 to Provide the OSI Connection-mode Network Service for ITU-T Applications, November 1993, (Geneva), ITU, ITU-T Telecommunication Standardization Sector of ITU. (Previously "CCITT Recommendation") <http://www.itu.int/rec/T-REC-X.223/>
[5]: 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>
[6]: C411 (XX25), X/Open CAE Specification: X.25 Programming Interface using XTI (XX25), November 1995, (Berkshire, UK), X/Open, Open Group Publication. [ISBN: 1-85912-136-5] <http://www.opengroup.org/onlinepubs/>
[7]: Solstice® X.25, Solstice® X.25 9.2 Programming Guide, October 1999, (Palo Alto, California), Sun Microsystems, Inc., Sun. [Part No: 806-1235-10] <http://docs-pdf.sun.com/>
[8]: IRIX® SX.25, SX.25 NLI Programming's Guide, 1994, (Mountainview, California), Silicon Graphics, Inc., SGI Technical Publications. [Doc. No: 007-2268-002] <http://techpubs.sgi.com/>
[9]: PT X.25, X.25 Protocol User's Manual, 2007, (Rochester, New York), Performance Technologies Inc., PT.

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 X.25 Networking: Package strx25 version 0.9.2.1 released 2008-10-31.

Index

NAME
INTERFACE
SYNOPSIS
DESCRIPTION
FORMAT
MEMBERS
RESPONSE
USAGE
NOTICES
FILES
SEE ALSO
COMPATIBILITY
CONFORMANCE
HISTORY
VERSIONS
REFERENCES
TRADEMARKS
IDENTIFICATION

This document was created by man2html, using the manual pages.
Time: 09:24:43 GMT, May 21, 2013