As per Relevance of the word datagram, we have this rfc below:

---

Network Working Group J. T.
Request for Comments: 877 Purdue
September 1983



A Standard for the Transmission of IP

Public Data




This RFC specifies a standard adopted by CSNET, the VAN gateway,
other organizations for the transmission of IP datagrams over
X.25-based public data networks.

An X.25 virtual circuit is opened on demand when a datagram arrives
the network interface for transmission. A virtual circuit is
after some period of inactivity (the length of the period depends
the cost associated with an open virtual circuit). A virtual
may also be closed if the interface runs out of virtual circuits.
algorithm for managing virtual circuits during peak demand is
in [1].



1.1 The first octet in the Call User Data Field (the first data
in the Call Request packet) is used for protocol demultiplexing
The value hex CC (binary 11001100, decimal 204) is used to
INTERNET PROTOCOL.

1.2 IP datagrams are sent as X.25 "complete packet sequences". That is
datagrams begin on packet boundaries and the M bit ("more data")
used for datagrams that are larger than one packet. There are
additional headers or other data in the packets

1.3 Unless a larger packet size is negotiated, the maximum size of
IP datagram transmitted over X.25 is 576 octets. If two
negotiate a large X.25 packet size (for example, 1024 octets),
IP datagram of that size is allowed.

1.4 Either site may close a virtual circuit. If the virtual circuit
closed or reset while a datagram is being transmitted, the
is lost

GENERAL

2.1 Protocols above IP, such as TCP, do not affect this standard.
particular, no attempt is made to open X.25 virtual
corresponding to TCP connections




Korb [Page 1]

RFC 877 September 1983
Transmission of IP Datagrams Over Public Data


2.2 Features of X.25 not discussed in this document are not used
For example, interrupt packets and the D bit (
end-to-end significance) are not used

2.3 Negotiable features (facilities) of X.25 are allowed.
example, sites are free to negotiate larger packet and
sizes

2.4 Some sites, such as CSNET sites, may attempt to open
virtual circuits to a single site. Sites should attempt
handle such incoming calls gracefully: transmit on
additional circuits if possible and accept incoming
from them, but do not accept the CALL REQUEST, only
immediately close the connection or ignore
transmitted on such circuits




[1] Comer, D.E. and Korb, J.T., "CSNET Protocol Software:
IP-to-X.25 Interface", SIGCOMM Symposium on
Architectures and Protocols, March 1983.




























Korb [Page 2]

---

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

---