As per Relevance of the word connection, we have this rfc below:
Network Working Group J.
Request for Comments: 1086
M.
December 1988
ISO-TP0 bridge between TCP and X.25
Status of this
This memo proposes a standard for the Internet community. Hosts
the Internet that choose to implement ISO TP0 transport
between TCP and X.25 based hosts are expected to experiment with
proposal. TCP port 146 is reserved for this proposal.
of this memo is unlimited and comments are highly encouraged
This memo specifies a protocol that is used to bridge ISO TP0
between X.25 and TCP networks. This technique is useful
interconnecting a DDN IP internet to an X.25 subnetwork. This is
a "magic bullet" solution to the DDN/ISO interoperability problem
Rather, if one is running higher-layer ISO protocols in both
(namely ISO TP0), then a TP0 bridge can be used to
connectivity
The protocol itself is fairly simple as the method of operation
running TP0 over the TCP and X.25 protocols have previously
defined. A bridge offering ISO-TP0 gateway services simply
both methods as appropriate. The protocol works by TP0/TCP
"registering" an X.25 subaddress (and corresponding TCP port/
address) with the bridge. TP0/X.25 hosts use the standard method
establishing, maintaining, and releasing connections. When
connection is established, the bridge establishes the
TCP connection and simply shuffles TP0 packets between the two.
a TP0/TCP host initiates a connection, it establishes a
connection to the bridge using port number 146 and communicates
desired X.25 address. The bridge establishes a connection to
native X.25 host and simply shuffles TP0 packets between the two
1. Introduction and
The migratory protocol described in [RFC1006] makes possible
transmission of TP0 packets between hosts on TCP/IP internets.
the addition of a small protocol converter, a TCP/IP host can be
to appear in the X.25 addressing space and be able to accept and
Onions & Rose [Page 1]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
connections using the TP0 protocol
This procedure is particularly useful in the following cases
1. A host on an IP based internet can communicate with hosts
X.25 based networks providing the hosts are running ISO protocols
This also assumes a friendly gateway willing to run the actual TP
bridge and make available to the IP host part of its X.25
space
2. A site having sparse connections to an X.25 network and
a TCP/IP based local area network for local communications.
this case all hosts on the LAN can have access to hosts on
X.25 network running ISO TP0.
Pictorially, this memo describes interoperation in the
environment
+---------------------------------+
| |
| +-----------------------------------+
| +----+ | +----+ | +----+ |
| | | | | | | | | |
| | +-----------|-----+ +--------------+ | |
| | | TP0 | | | | TP0 | | |
| +----+ | +----+ | +----+ |
| TCP Host | Bridge Host| X.25 Host |
| | | |
| | | |
| | | |
+-------------------|-------------+ |
TCP/IP Network | |
| |
+-----------------------------------+
X.25
2. Definitions and
Some modest terminology and philosophy is introduced to
readability and stir interest
The ISO Transport Service (TS) provides a reliable, packet-stream
its users [ISO8072]. The ISO Transport Protocol (TP) implements
service [ISO8073]. There are five classes of this protocol.
class is selected on the basis of the services offered by
underlying network service. Transport class 0 (TP0) is used when
network service offered is connection-oriented and error-detecting
Onions & Rose [Page 2]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
As should be expected, TP0 is a rather simple protocol, since
underlying network service actually provides most of the
offered by the transport service
CCITT Recommendation X.25 [ISO8208,X.25] offers such a
service. It is beyond the scope of this memo to describe X.25 in
detail, but two observations are pertinent: First, X.25 is
as a wide-area network service by many commercial and (non-U.S.)
government carriers. Second, the TP0/X.25 combination is
popular in Europe and other communities with a strong PTT-
market
It has been argued that the DoD Transmission Control Protocol (TCP
[MIL1778, RFC793] can also be seen as providing a connection-
and error-detecting network service. This remark is controversial
the sense that the TCP is actually an end-to-end transport
and not a network protocol; the DoD Internet Protocol (IP) [MIL1777,
RFC791] is the network protocol in the DoD Protocol Suite. However
one of the advantages of layering is that, when properly architected
it enhances flexibility. This notion led to the development
[RFC983] and its successor [RFC1006], which described how to
the ISO transport service on top of TCP/IP internetworks
3. The
The model is simple. The method for transmitting TP0 packets
TCP is defined in [RFC1006]. The method for transmitting TP0
using X.25 is defined in [ISO8878]. The TP0 bridge merely has
convert between the two forms. As with most protocols, there
three well-defined phases of interaction: connection establishment
data transfer, and connection release. The method of operation
the data transfer and connection release phases are quite
when using TP0 over either network service. Hence the
protocol mapping functions are quite simple
The difficult part is in managing connection establishment. A
"registration" protocol is used to aid the protocol mapping
for the connection establishment phase. The protocol performs one
two operations: an X.25 address is specified for an outgoing call,
an X.25 address is specified to accept incoming calls
This memo ignores the problems of authentication and authorization
These areas are presumed to be a local matter. It is worth
out that running such a TP0 bridge with unrestricted access
any TCP/IP host to lay claim to part of the TP0 bridge host's X.25
address space. This address space is limited and will not
many foreign hosts registering listening addresses
Onions & Rose [Page 3]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
The protocol makes no attempt to report errors other than
transmitted by the TP0 protocol. To attempt such additions
require other mechanism such as a new protocol layer or equivalent
The chosen model is kept as simple as possible with network
being ignored if recoverable, and resulting in
otherwise. This actually enhances the transparency of the gateway
in that the only gateway specific functions are collected together
the connection phase. The resultant circuit, once established,
indistinguishable from an [RFC1006] implementation
4. The
The protocol is quite simple. A successful connection
phase results in two network connections being established. TP0
used over each network connection, though one network connection
provided by X.25 and the other by the TCP
During the data transfer phase, the TP0 bridge reads TPDUs (
protocol data units) from one network connection and writes them
the other network connection. During the connection release phase
when one network indicates a disconnect, the bridge disconnects
other network connection; or in the case of simultaneous
disconnects, no action is taken by the bridge
As expected, the method of operation for the connection
phase is more complex. Connection establishment is driven by
registration procedure which is initiated by a TCP/IP host
a connection with the TP0 bridge. This procedure takes on one of
"flavors" depending on whether the initiating host wishes
establish a connection to a particular X.25 address or listen
connections on a particular X.25 address
The initiating host initiates the registration procedure
establishing a connection to TCP port 146 on the TP0 bridge. It
sends one octet which indicates the flavor the registration
will take
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| function |
+-+-+-+-+-+-+-+-+
Onions & Rose [Page 4]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
The value of this octet is a binary-encoded value
value
----- -------
0
1 connect to a particular X.25
2 listen for incoming X.25
3-255
The method of operation for the registration procedure now diverges
based on the function chosen
FUNCTION 1: CONNECTION THROUGH THE TP0
The X.25 address to call is now sent by the initiating host to
TP0 bridge. The format of an X.25 address is described in
5 of this memo
The TP0 bridge now attempts to call the specified address.
this succeeds, the connection establishment phase has
and the data transfer phase is begun. If the call fails, then
TP0 bridge closes the TCP connection
FUNCTION 2: ESTABLISHING A LISTENING
The X.25 address, which should be a subaddress of the TP0 bridge'
X.25 address, on which to listen for incoming X.25 connections
now sent by the initiating host to the TP0 bridge
Next, the initiating host sends an IP address and TCP port
which will service incoming calls for the indicated X.25 address
The format of a TCP/IP address is described in Section 6 of
memo
The TP0 bridge now listens, on behalf of the initiating host,
the indicated X.25 address
If an incoming call is received, a TCP connection is
to the corresponding TCP/IP address. If this connection
successful, then the connection establishment phase has
and the data transfer phase is begun. If the connection fails
the incoming call is refused
The TCP/IP connection between the initiating host and the TP
bridge is a "heartbeat" connection for the registration function
If this connection closes, the TP0 bridge assumes hat
listening function has been terminated by the initiating host,
consequently, the TP0 bridge no longer listens for incoming
Onions & Rose [Page 5]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
on the indicated X.25 address. If such a facility were
present, then the indicated X.25 address could not be
for reuse
5. Format of X.25
A standardized octet-encoding of X.25 addresses is used by
protocol described in this memo. The encoding has a fixed-length
68 octets and contains 10 fields
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| address type | X.121 address ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... | ... | ... |
| ... | ... | ... | ... |
| ... | ... | ... | ... |
| ... | ... | X.121 length | Protocol ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ... | ... | PID length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Call User Data field | ... | ... |
| ... | ... | ... | ... |
| ... | ... | ... | ... |
| ... | ... | ... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CUDF length | X.25 Facilities ... | ... |
| ... | ... | ... |Facility Length
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The fields are
address type (2 octets) - a binary-encoded value in network
indicating the address type. The value 3 is used for X.25
of this format
X.121 address (16 octets) - the ascii-encoded value of the X.121
address
address length (1 octet) - a binary-encoded value in network
indicating how many octets of the X.121 address are meaningful
Protocol ID (4 octets) - meaningful at the remote system
Protocol ID length (1 octet) - a binary-encoded value indicating
number of protocol ID octets are meaningful
Onions & Rose [Page 6]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
User Data (16 octets) - meaningful at the remote system
User Data Length (1 octet) - a binary-encoded value indicating
number of User Data octets are meaningful
X.25 Facilities (6 octets) - meaningful at the remote system
X.25 Facilities length (1 octet) - a binary-encoded value
the number of Facility octets are meaningful
6. Format of TCP/IP
A standardized octet-encoding of TCP/IP addresses is used by
protocol described in this memo. The encoding has a fixed-length
16 octets and contains 4 fields
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| address type | TCP port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | ... | ... | ... |
| ... | ... | ... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The fields are
address type (2 octets) - a binary-encoded value in network order
The value 2 is used
TCP port (2 octets) - a binary-encoded value in network order
IP address (4 octets) - a binary-encoded value in network order
reserved (16 octets) - null-value padding
At present, the structure of the X.25 address and the
address are rather ad-hoc and specific to the UNIX operating system
These structures may change in the future as experience is gained
the use of the TP0 bridge
Onions & Rose [Page 7]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
[ISO8072] Information processing systems -- Open
interconnection, "Transport Service Definition",
International Standard, June, 1985.
[ISO8073] Information processing systems -- Open
interconnection, "Transport Protocol Specification",
International Standard, July, 1986.
[ISO8208] Information processing systems, "X.25 package
protocol for data terminal equipment",
International Standard, July, 1985.
[ISO8878] Information processing systems -- Data communications
Use of X.25 to provide the OSI connection-mode
service", Draft International Standard, January, 1987.
[MIL1777] Military Standard 1777, "Internet Protocol".
[MIL1778] Military Standard 1778, "Transmission Control Protocol".
[RFC791] Postel, J., "Internet Protocol - DARPA Internet
Protocol Specification", RFC 791, USC/ISI
September 1981.
[RFC793] Postel, J., "Transmission Control Protocol -
Internet Program Protocol Specification", RFC 793,
USC/ISI, September 1981.
[RFC983] Cass, D., and M. Rose, "ISO Transport Services on
of the TCP", RFC 983, NTRC, April 1986.
[RFC1006] Rose, M., and D. Cass, "ISO Transport Service on
of the TCP Version: 3", NTRC, May 1987.
[X.25] CCITT Recommendation X.25, "Interface Between
Terminal Equipment (DTE) and Data Circuit
Equipment (DCE) for Terminals Operating in the
Mode on Public Data Networks," International
and Telephone Consultative Committee Yellow book, Vol
VIII.2, Geneva, 1981.
Onions & Rose [Page 8]
RFC 1086 ISO-TP0 bridge between TCP and X.25 December 1988
Authors' Addresses
Julian P.
Computer Science
Nottingham
University
Nottingham, NG7 2
United
EMail: JPO@CS.NOTT.AC.
Marshall
The Wollongong
1129 San Antonio
Palo Alto, CA 94303
Phone: (415) 962-7100
EMail: mrose@TWG.
Onions & Rose [Page 9]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
