Technical Standard: Networking Services (XNS), Issue 5.2 Draft 2.0
Copyright © 1999 The Open Group
abortive releaseAn abrupt termination of a transport connection, which may result
in the loss of data.
asynchronous modeThe mode of execution in which transport
service functions do not wait for specific
asynchronous events to occur before returning control to the user, but instead
return immediately if the event is not pending.
CLConnectionless (a deprecated synonym for "connectionless-mode").
COConnection-oriented (a deprecated synonym for "connection-mode").
connection establishmentThe phase in connection-mode that enables two transport users to create
a transport connection between them.
connection-modeA mode of transfer where a logical link is established between two endpoints.
Data is passed over this link by a sequenced and reliable way.
connectionless-modeA mode of transfer where different units of data are passed through the
network without any relationship between them.
connection releaseThe phase in connection-mode that terminates a previously established
transport connection between two users.
datagramA unit of data transferred between two users of the connectionless-mode
data transferThe phase in connection-mode or connectionless-mode that supports the
transfer of data between two transport users.
DNSThe Domain Name System defined in RFC 1035.
This system provides translation between host names and Internet
expedited dataData that are considered urgent. The specific semantics of
expedited data are defined by the transport provider that provides the
ETSDUExpedited Transport Service Data Unit
expedited transport service data unitThe amount of expedited user data, the identity of which is preserved
from one end of a transport connection to the other (that is, an
FQDNFully-qualified domain name.
host byte orderThe implementation-dependent byte order supported by the local host machine
(see the Glossary entry for "Network Byte Order").
Functions are provided to convert 16 and 32-bit values between network and
host byte order (see
initiatorAn entity that initiates a connection request.
ISOInternational Organization for Standardization
An item marked "LEGACY" in this specification means that
it is being retained for compatibility with older
applications, but has limitations which makes it inappropriate for
developing portable applications.
New applications should use alternative means of obtaining equivalent
network byte orderThe byte order in which the most significant byte of a multibyte
integer value is transmitted first. This byte order is the standard
byte order for Internet protocols.
network host databaseA database whose entries define the names and network addresses
of host machines. See
network net databaseA database whose entries define the names and network numbers of
network protocol databaseA database whose entries define the names and protocol numbers of
network service databaseA database whose entries define the names and local port numbers of
orderly releaseA procedure for gracefully terminating a transport connection with no
loss of data.
OSIOpen System Interconnection
responderAn entity with whom an initiator wishes to establish a transport connection.
socketA communications endpoint associated with a file descriptor that
provides communications services using a specified communications
SVIDSystem V Interface Definition
synchronous modeThe mode of execution in which transport service functions wait for specific
asynchronous events to occur before returning control to the user.
TCPTransmission Control Protocol
TLITransport Level Interface
transport addressThe identifier used to differentiate and locate specific transport endpoints
in a network.
transport connectionThe communication circuit that is established between two transport
users in connection-mode.
transport endpointThe communication path, which is identified by a file descriptor,
between a transport user and a specific transport provider.
A transport endpoint is called passive before, and active after,
a relationship is established,
with a specific instance of this
transport provider, identified by the TSAP.
transport provider identifierA character string used by the
function to identify the transport service provider.
transport service access pointA TSAP is a uniquely identified instance of the transport provider.
A TSAP is used to identify a transport user on a certain endsystem.
In connection-mode, a single TSAP may have more than one connection
established to one or more
each individual connection then is identified
by a transport endpoint at each end.
transport service data unitA unit of data transferred across the transport service with boundaries
and content preserved unchanged.
A TSDU may be divided into sub-units
passed between the user and XTI.
The T_MORE flag is set in all but
the last fragment of a TSDU sequence
constituting a TSDU.
The T_MORE flag implies nothing about
how the data is handled and passed
to the lower level by
the transport provider, and how they are delivered to the remote user.
transport service providerA transport protocol providing the service of the transport layer.
transport service userAn abstract representation of the totality of those entities within a single
system that make use of the transport service.
TSAPSee Transport Service Access Point
TSDUSee Transport Service Data Unit
UDPUser Datagram Protocol
user applicationThe set of user programs, implemented as one or more process(es)
in terms of UNIX
semantics, written to realise a task, consisting of a
set of user required functions.
XTIX/Open Transport Interface
XEMX/Open Event Management Interface