TCP
Click on the red underlined text to get to the source
... There are two basic approaches which can be taken when "porting" ISO
applications to TCP/IP ([RFC793],[RFC791]) and IPv6 ...
... environments. One approach is to port each individual application
separately, developing local protocols on top of TCP. A second
approach is based on the notion of layering the ISO Transport Service ...
... ISO Transport Service
over TCP/IP. This approach solves the problem for all applications
which use the ISO Transport Service ...
...
The 'well known' TCP port 102 is reserved for hosts which implement
the Protocol described in this document. Note that the Protocol does
...
... hosts which implement
the Protocol described in this document. Note that the Protocol does
not mandate the use of TCP port 102 for all connections.
...
... ISO 8348 CONS. This document specifies how to operate class 0
and 2 over TCP. This document does not prevent use of other classes
from operating over TCP ...
... TCP. This document does not prevent use of other classes
from operating over TCP, but their specification is beyond the scope
of this document.
...
... +--------------------------------------------------+
|
|-TCP as a Connection Oriented Network Service
...
... ISO Transport Protocol (with some
extensions) running over TCP. Two variants of the protocol are
defined, "Class 0 over TCP ...
... TCP. Two variants of the protocol are
defined, "Class 0 over TCP" and "Class 2 over TCP", which are based
...
... User. It also defines the mapping between the Network Service
Definition and the TCP Service Definition.
...
...
The mapping between, ISO 8348 CONS primitives and TCP Service
primitives, defined in this document assumes that the TCP ...
... TCP Service
primitives, defined in this document assumes that the TCP offers the
following service primitives:
...
... connection has errored and is now closed
TCP-CLOSED
- an orderly disconnection has started
...
... Mapping TCP as a Network Service Provider ...
... IPv4 or IPv6 address using
the selected TCP port. When the TCP signals either success or
failure, this results in an N-CONNECT ...
... IPv6 address using
the selected TCP port. When the TCP signals either success or
failure, this results in an N-CONNECT.INDICATION action.
...
... In order to await a N-CONNECT.INDICATION event, a server performs a
TCP-LISTEN_PORT to the selected TCP port. When a client ...
... client successfully
connects to this port, the TCP-CONNECTED event occurs and an implicit
N-CONNECT.RESPONSE action is performed.
...
...
TCP port 102 is reserved for implementations conforming to this
specification. Use of any TCP port is conformant to this
...
... TCP port 102 is reserved for implementations conforming to this
specification. Use of any TCP port is conformant to this
specification.
...
... data unit (TPDU), encapsulates the
TPDU in a discrete unit called TPKT and uses the TCP-SEND_DATA
primitive. Please also refer to 'Notes to Implementors ...
...
In order to trigger a N-DATA.INDICATION action, the TCP indicates
that data is ready through TCP-DATA_READY event and a TPKT is read
...
... N-DATA.INDICATION action, the TCP indicates
that data is ready through TCP-DATA_READY event and a TPKT is read
using the TCP-READ_DATA primitive.
...
... that data is ready through TCP-DATA_READY event and a TPKT is read
using the TCP-READ_DATA primitive.
...
...
In order to trigger a N-DISCONNECT.INDICATION, the TCP indicates that
the connection has been closed through TCP ...
... TCP indicates that
the connection has been closed through TCP-CLOSE event. If the TCP
connection has failed the TCP indicates that the connection ...
... the connection has been closed through TCP-CLOSE event. If the TCP
connection has failed the TCP indicates that the connection has been
...
... connection has been closed through TCP-CLOSE event. If the TCP
connection has failed the TCP indicates that the connection has been
closed through TCP ...
... TCP indicates that the connection has been
closed through TCP-ERRORED event, this trigger a N-
DISCONNECT.INDICATION.
...
...
The ED TPDU is sent inband on the same TCP connection as all of the
other TPDUs.
...
... Transport Disconnection is based on the NS-provider (TCP)
Disconnection and is therefore disruptive.
...
... sender of an
ED TPDU shall send the ED TPDU on both the Normal Data and
Expedited Data TCP connections. Transmission of subsequent DT TPDU
will not be interrupted. The receiver of ED TPDU counts how many
...
... will not be interrupted. The receiver of ED TPDU counts how many
ED TPDU it has seen on each TCP connection, and will only deliver
to the TS-User the ED TPDU from the TCP connection ...
... TCP connection, and will only deliver
to the TS-User the ED TPDU from the TCP connection with the higher
count.
...
... Data transfer, there are two possible
procedures for the establishment and assignment of the Expedited
Data TCP connection. Which one is used is negotiated during
connection establishment.
...
... Connection" procedure and "Reverse Connection"
procedure guarantee independence of the Normal Data TCP connection
from the Expedited Data TCP connection. They also ensure that a
...
... procedure guarantee independence of the Normal Data TCP connection
from the Expedited Data TCP connection. They also ensure that a
busy Normal Data TCP connection cannot block an Expedited Data TCP
connection ...
... from the Expedited Data TCP connection. They also ensure that a
busy Normal Data TCP connection cannot block an Expedited Data TCP
connection.
...
... TCP connection. They also ensure that a
busy Normal Data TCP connection cannot block an Expedited Data TCP
connection.
...
...
The Expedited Data TCP connection created by either procedure must
be between the same pair of hosts ...
... created by either procedure must
be between the same pair of hosts as the Normal Data TCP
connection, must not be shared among Transport Connections, and
must remain established until the Transport Connection ...
... created for Expedited Data transfer should also use
the TCP primitives defined in this document.
...
... ISO 8073. This procedure allows a transport connection
to make use of multiple TCP connections. Please refer to 'Notes to
Implementors' section 6.9.
...
... initiator of a Transport
Connection creates a Normal Data TCP connection using an
arbitrarily-chosen local TCP port 'x' and a known remote TCP port ...
... creates a Normal Data TCP connection using an
arbitrarily-chosen local TCP port 'x' and a known remote TCP port
(either the ITOT ...
... TCP connection using an
arbitrarily-chosen local TCP port 'x' and a known remote TCP port
(either the ITOT well-known port ...
... well-known port, or some other). The initiator
listens for an incoming TCP connection on the TCP port 'x'. The
responder ...
... initiator
listens for an incoming TCP connection on the TCP port 'x'. The
responder of the Transport Connection ...
... responder of the Transport Connection must create a second TCP
connection (to be used for Expedited Data) using an arbitrarily-
chosen local TCP port 'y' and the remote TCP port ...
... create a second TCP
connection (to be used for Expedited Data) using an arbitrarily-
chosen local TCP port 'y' and the remote TCP port 'x' , before it
can issue a CC ...
... TCP
connection (to be used for Expedited Data) using an arbitrarily-
chosen local TCP port 'y' and the remote TCP port 'x' , before it
can issue a CC TPDU on the Normal Data TCP connection ...
... TCP port 'x' , before it
can issue a CC TPDU on the Normal Data TCP connection. The
initiator need not listen for further TCP connections ...
... TCP connection. The
initiator need not listen for further TCP connections on port 'x'
after the Expedited Data TCP connection ...
... expected by ISO Transport is that the TCP manages a continuous stream
of octets, with no explicit boundaries.
...
... TCP Connection Establishment ...
... they will be told by the network service provider (in this case
TCP/IP) when the network connection being used to transmit their
TPDUs is unexpectedly terminated. It is therefore strongly suggested
...
... network connection being used to transmit their
TPDUs is unexpectedly terminated. It is therefore strongly suggested
that the TCP keep alive mechanism be selected, as this ensures
reporting of network connection loss.
...
... TCP Data transfer ...
... performance reason it is suggested that the Nagle algorithm [RFC896] be disabled (using the TCP_NODELAY socket option). This feature
allows TPKT data to be sent without delay.
...
... service it is a wasted effort to use "Expedited Data
Acknowledgement", since ED TPDUs are duplicated and sent on both the
Normal Data and Expedited Data TCP connections.
...
... Recombination procedure, which associates Data (normal and expedited)
TPDUs arriving for a transport connection over two TCP connections
must be handled.
...
...
It is legal to send Expedited Data TPDU inband on the Normal Data TCP
connection.
...
...
Please note that the protocol specified in this document does not
define when an Expedited Data TCP connection should be established.
This is an implementation choice.
...
... Non-blocking Expedited Data" service it is recommended to
not delay establishing Expedited Data TCP connection.
...
... negotiation. The
protocol described in this document introduces Class 2 over TCP, and
it therefore introduces the need to be able to perform class
...
... Security issues are not specifically addressed in this document.
Operation of this protocol is no more and no less secure than
operation of TCP and ISO 8073 protocols. The reader is directed there
for further reading.
...
... Rose, M., and D. Cass, "ISO Transport Services on Top of the TCP Version 3", STD 35, RFC 1006std35 ...
... Transport Class 2 Non-use of Explicit Flow Control over TCP - RFC1006 extension", RFC 1859, October 1995. ...