Endangered packet species conservation

X.25
http://www.farsite.com/X.25/X.25_info/X.25.htm
http://www.rhyshaden.com/x25.htm
http://rhizome.org/editorial/2014/may/23/interview-Borka-Jerman-Blazic/


Encapsulation 
   It is sometimes desirable to transport X.25 over IP internets.  The
   X.25 Packet Level requires a reliable link level below it and
   normally uses LAPB.  This memo documents a method of sending X.25
   packets over IP internets by encapsulating the X.25 Packet Level in
   TCP packets.
http://tools.ietf.org/rfcmarkup?rfc=1613





4. X.25 Packet in captivity:
                  -------------------------------+
                  |                                            |
                  |       IP Header                   |
                  |                                            |
                  -------------------------------+
                  |                               |
                  |       TCP Header              |
                  |                               |
                  ---------------------------------
                  |                               |
                  |       XOT Header              |
                  |                               |
                  ---------------------------------
                  |                               |
                  |       X.25  Packet            |
                  |                               |
                  ---------------------------------

 Viceversa it could have ended like this:
          
    X.25 data packets:

    +----------------+------------------------+
    | GFI, LCN, I    | IP datagram            |
    +----------------+------------------------+
          
https://tools.ietf.org/rfc/rfc1356.txt

---

PAD!
A packet assembler/disassembler, abbreviated PAD is a communications device which provides multiple asynchronous terminal connectivity to an X.25 (packet-switching) network or host computer. It collects data from a group of terminals and places the data into X.25 packets (assembly). 

---

A series of un-encapsulated X.25 packets have been found during the session:
   
../images/x25_packets_over_wireless.png

    Apparently they are sent by the fritzbox and by the pipelines server

---



---

UUCP
In 1979, two students at Duke University, Tom Truscott and Jim Ellis, originated the idea of using Bourne shell scripts to transfer news and messages on a serial line UUCP connection

TCP/IP
The importance of being 'network-agnostic'

In 1988, Daniel Karrenberg, from Centrum Wiskunde & Informatica (CWI) in Amsterdam, visited Ben Segal, CERN's TCP/IP Coordinator, looking for advice about the transition of the European side of the UUCP Usenet network (much of which ran over X.25 links) over to TCP/IP. In 1987, Ben Segal had met with Len Bosack from the then still small company Cisco about purchasing some TCP/IP routers for CERN, and was able to give Karrenberg advice and forward him on to Cisco for the appropriate hardware. This expanded the European portion of the Internet across the existing UUCP networks, and in 1989 CERN opened its first external TCP/IP connections.[39] This coincided with the creation of Réseaux IP Européens (RIPE), initially a group of IP network administrators who met regularly to carry out coordination work together. Later, in 1992, RIPE was formally registered as a cooperative in Amsterdam.

//
(Ben Segal)
He played an important role as an Internet promoter, spearheading the introduction of IP into a hostile Europe when it was not politically correct or career-friendly to do so there. European Postal Telegraph and Telecommunications Administrations and industry were opposed to these standards, and their use outside the laboratory was forbidden. Segal began working on early data communications at CERN in 1971, but it was in 1977, on a sabbatical in Palo Alto, that he first encountered both the ARPAnet and Unix. -

Chaosnet

"Chaosnet was first developed by Thomas Knight and Jack Holloway at MIT's AI Lab in 1975 and thereafter. It refers to two separate, but closely related, technologies. The more widespread was a set of computer communication packet-based protocols intended to connect the then-recently developed and very popular (within MIT) Lisp machines; the second was one of the earliest local area network (LAN) hardware implementations."  https://en.wikipedia.org/wiki/Chaosnet


CYCLADES

https://en.wikipedia.org/wiki/CYCLADES

The CIGALE network featured a distance vector routing protocol, and allowed experimentation with various metrics. it also included a time synchronization protocol in all the packet switches. CIGALE included early attempts at performing congestion control by dropping excess packets.
The name CIGALE—(French pronunciation: ?[si?al]) which is French for cicada—originates from the fact that the developers installed a speaker at each computer, so that "it went 'chirp chirp chirp' like cicadas" when a packet passed a computer (Gillies and Cailliau 2000:38[2]).

Demise
By 1976, the French PTT was developing Transpac, a packet network based on the emerging X.25 standard. The academic debates between datagram and virtual circuit networks continued for some time, but were eventually cut short by bureaucratic decisions.
Data transmission was a state monopoly in France at the time, and IRIA needed a special dispensation to run the CYCLADES network. The PTT did not agree to funding by the government of a competitor to their Transpac network, and insisted that the permission and funding be rescinded. By 1981, Cyclades was forced to shut down.