npi.7.man

This a separate release of the OpenSS7 X/Open XTI/TLI library, TLI modules (timod, tirdwr) and the I

'\" rtp
.\" -*- nroff -*- vim: ft=nroff noautoindent nocindent nosmartindent
.\"
.\" @(#) npi.7.man,v 0.9.2.3 2004/05/16 02:35:49 brian Exp
.\"
.\" =========================================================================
.\"
.\" Copyright (C) 2001-2004  OpenSS7 Corporation <www.openss7.com>
.\"
.\" All Rights Reserved.
.\"
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Permission is granted to copy and distribute modified versions of this
.\" manual under the conditions for verbatim copying, provided that the
.\" entire resulting derived work is distributed under the terms of a
.\" permission notice identical to this one
.\" 
.\" Since the Linux kernel and libraries are constantly changing, this
.\" manual page may be incorrect or out-of-date.  The author(s) assume no
.\" responsibility for errors or omissions, or for damages resulting from
.\" the use of the information contained herein.  The author(s) may not
.\" have taken the same level of care in the production of this manual,
.\" which is licensed free of charge, as they might when working
.\" professionally.
.\" 
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.\" -------------------------------------------------------------------------
.\"
.\" U.S. GOVERNMENT RESTRICTED RIGHTS.  If you are licensing this Software
.\" on behalf of the U.S. Government ("Government"), the following
.\" provisions apply to you.  If the Software is supplied by the Department
.\" of Defense ("DoD"), it is classified as "Commercial Computer Software"
.\" under paragraph 252.227-7014 of the DoD Supplement to the Federal
.\" Acquisition Regulations ("DFARS") (or any successor regulations) and the
.\" Government is acquiring only the license rights granted herein (the
.\" license rights customarily provided to non-Government users).  If the
.\" Software is supplied to any unit or agency of the Government other than
.\" DoD, it is classified as "Restricted Computer Software" and the
.\" Government's rights in the Software are defined in paragraph 52.227-19
.\" of the Federal Acquisition Regulations ("FAR") (or any success
.\" regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the
.\" NASA Supplement to the FAR (or any successor regulations).
.\"
.\" =========================================================================
.\" 
.\" Commercial licensing and support of this software is available from
.\" OpenSS7 Corporation at a fee.  See http://www.openss7.com/
.\" 
.\" =========================================================================
.\"
.\" Last Modified 2004/05/16 02:35:49 by brian
.\"
.\" =========================================================================
.so strxnet.macros
.R1
bracket-label "\fR[\fB" "\fR]" "\fR, \fB"
no-default-database
database strxnet.refs
accumulate
move-punctuation
abbreviate A
join-authors ", " ", " " and "
et-al " et al" 2 3
abbreviate-label-ranges ".."
sort-adjacent-labels
.R2
.\"
.\"
.TH NPI 7 "2004/05/16 02:35:49" "strxnet-0_9_2-4" "Linux STREAMS"
.SH NAME
.B NPI
\- Network Provider Interface
.SH DESCRIPTION
.\"
.\"
.\"
.\"
.\"
.PP
This document specifies a
.IR STREAMS (4)-based
kernel-level instantiation of the
ISO/CCITT network service definition.  The Network Provider Interface (NPI)
enables the user of a network layer service to access and use any of a variety
of conforming network layer service providers without specific knowledge of the
provider's protocol.  The service interface is designed to support any
connection-mode network protocol and connectionless network protocol.  This
interface only specifies access to network layer service providers, and does
not address issues concerning network layer management,protocol performance,
and performance analysis tools.
.PP
The specification assumes that the reader is familiar with the OSI reference
model terminology, ISO/CCITT Network Layer Service, and
.IR STREAMS (4).
.SS "Related Documentation"
.IP \(em \w'\(em\(em'u
1986 CCITT X.213 Recommendation [1]
.IP \(em \w'\(em\(em'u
ISO 8348 [2]
.IP \(em \w'\(em\(em'u
ISO 8348/AD1 [3]
.IP \(em \w'\(em\(em'u
ISO 8473 [4]
.IP \(em \w'\(em\(em'u
ISO 8208 [5]
.IP \(em \w'\(em\(em'u
ISO 8878 [6]
.IP \(em \w'\(em\(em'u
System V Interface Definition, Issue 2 - Volume 3 [7]
.SS "Role"
.PP
This document specifies an interface that supports the service provided by the
Network Services Definition for Open Systems Interconnection for CCITT
Applications as described in CCITT Recommendation X.213 and ISO 8348 (for
CONS) and ISO8348/Addendum 1 (for CLNS).  These specifications are targeted for
use by developers and testers of protocol modules that require network layer
service.
.SS "Definitions, Acronyms, and Abbreviations"
.TP 18
.I Calling NS user
An NS user that initiates a Network Connection (NC).
.TP
.I Called NS User
An NS user with whom a calling NS user wishes to establish a network connection (NC).
.TP
.I CLNP
Connection-less Network Protocol
.TP
.I CLNS
Connection-less Network Service.
.TP
.I CONP
Connection Oriented Network Protocol
.TP
.I CONS
Connection Oriented Network Service.
.TP
.I DLSAP
Data Link Service Access Point
.TP
.I ISO
International Organization for Standardization
.TP
.I NC
Network Connection
.TP
.I Network User
Kernel level protocol or user level application that is accessing the
services of the network layer.
.TP
.I Network Provider
Network layer entity/entities that provide/s the services of the network
interface.
.TP
.I NPI
Network Provider Interface
.TP
.I NS
Network Service.
.TP
.I NIDU
Network Interface Data Unit
.TP
.I NSAP
Network Service Access Point
.TP
.I NSDU
Network Service Data Unit
.TP
.I OSI
Open Systems Interconnection
.TP
.I QOS
Quality of Service.
.TP
.IR STREAMS (4)
A communication services development facility first available with UNIX System
V Release 3
.SS "The Network Layer"
The Network Layer provides the means to manage the operation of the network.
It is responsible for the routing and management of data exchange between
network-user entities.
.SS "Model of the NPI"
The NPI defines the services provided by the network layer to the network-user
at the boundary between the network layer and the network layer user entity.
The interface consists of a set of primitives defined as
.IR STREAMS (4)
messages that
provide access to the network layer services, and are transferred between the
NS user entity and the NS provider.  These primitives are of two types; ones
that originate from the NS user, and others that originate from the NS
provider.  The primitives that originate from the NS user make requests to the
NS provider, or respond to an event of the NS provider.  The primitives that
originate from the NS provider are either confirmations of a request or are
indications to the NS user that the event has occurred.
.PP
The NPI allows the NS provider to be configured with any network layer user
(such as the OSI Transport Layer) that also conforms to the NPI.  A network
layer user can also be a user program that conforms to the NPI and accesses
the NS provider via
.BR putmsg (2)
and
.BR getmsg (2)
system calls.
.SS "NPI Services"
The features of the NPI are defined in terms of the services provided by the
NS provider,and the individual primitives that may flow between the NS user
and the NS provider.
.PP
The services supported by the NPI are based on two distinct modes of
communication,connection (CONS) and connectionless (CLNS).  In addition, the
NPI supports services for local management.
.SS "CONS"
The main features of the connection mode communication are:
.IP a. 4
It is virtual circuit oriented;
.IP b. 4
It provides transfer of data via a pre-established path;
.IP c. 4
It provides reliable data transfer.
.PP
There are three phases to each instance of communication: Connection
Establishment;Data Transfer; and Connection Termination.  Units of data arrive
at their destination in the same order as they departed their source and the
data is protected against duplication or loss of data units within some
specified quality of service.
.SS "CLNS"
The main features of the connectionless mode communication are:
.IP a. 4
It is datagram oriented;
.IP b. 4
It provides transfer of data in self contained units;
.IP c. 4
There is no logical relationship between these units of data;
.IP d. 4
It is unreliable.
.PP
Connectionless mode communication has no separate phases.  Each unit of data
is transmitted from source to destination independently, appropriate addressing
information is included with each unit of data.  As the units of data are
transmitted independently from source to destination, there are, in general, no
guarantees of proper sequence and completeness of the data stream.
.SS "Local Management"
The NPI specifications also define a set of local management functions that
apply to both CONS and CLNS modes of communication.  These services have local
significance only.
.PP
Tables 1 and 2 summarizes the NPI service primitives by their state and
service.
.sp
.ce 1
.B TABLE 1.  Service Primitives for Connection Mode Data Transfer
.TS
tab(:) box center;
lb|lb|lbw(2.2i)s
l|l|ls.
STATE:SERVICE:PRIMITIVES
_
T{
.ad l
.hy 0
Local
Management
T}:T{
.ad l
.hy 0
Information
Reporting
T}:T{
.ad l
.hy 0
\fBN_INFO_REQ\fR(7),
\fBN_INFO_ACK\fR(7),
\fBN_ERROR_ACK\fR(7)
T}
:_:_
:Bind:T{
.ad l
.hy 0
\fBN_BIND_REQ\fR(7),
\fBN_BIND_ACK\fR(7),
\fBN_UNBIND_REQ\fR(7),
\fBN_OK_ACK\fR(7),
\fBN_ERROR_ACK\fR(7)
T}
:_:_
:T{
.ad l
.hy 0
Options
Management
T}:T{
.ad l
.hy 0
\fBN_OPTMGMT_REQ\fR(7),
\fBN_OK_ACK\fR(7),
\fBN_ERROR_ACK\fR(7)
T}
_
T{
.ad l
.hy 0
Connection
Establishment
T}:T{
.ad l
.hy 0
Connection
Establishment
T}:T{
.ad l
.hy 0
\fBN_CONN_REQ\fR(7),
\fBN_CONN_IND\fR(7),
\fBN_CONN_RES\fR(7),
\fBN_CONN_CON\fR(7),
\fBN_TOKEN_REQ\fR(7),
\fBN_TOKEN_ACK\fR(7),
\fBN_OK_ACK\fR(7),
\fBN_ERROR_ACK\fR(7)
T}
_
T{
.ad l
.hy 0
Connection
Mode Data Transfer
T}:T{
.ad l
.hy 0
Data
Transfer
T}:T{
.ad l
.hy 0
\fBN_DATA_REQ\fR(7),
\fBN_DATA_IND\fR(7),
\fBN_EXDATA_REQ\fR(7),
\fBN_EXDATA_IND\fR(7),
\fBN_DATACK_REQ\fR(7),
\fBN_DATACK_IND\fR(7)
T}