ArticleslgStudy

computer science

Interface Message Processor

Interface Message Processor is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Interface Message Processor rather than just read about it. In short: The Interface Message Processor (IMP) was the packet switching node used to interconnect participant networks to the ARPANET from the late 1960s to 1989. It was the first generation of gateways, which are known today as routers.

Interface Message Processor — main illustration
Interface Message Processor — illustration

Key takeaways

  • Interface Message Processor belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Interface Message Processor to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Interface Message Processor from memory before moving on to harder problems.

Reference excerpt

The Interface Message Processor (IMP) was the packet switching node used to interconnect participant networks to the ARPANET from the late 1960s to 1989. It was the first generation of gateways, which are known today as routers. An IMP was a ruggedized Honeywell DDP-516 minicomputer with special-purpose interfaces and software. In later years the IMPs were made from the non-ruggedized Honeywell 316 which could handle two-thirds of the communication traffic at approximately one-half the cost. An IMP requires the connection to a host computer via a special bit-serial interface, defined in BBN Report 1822. The IMP software and the ARPA network communications protocol running on the IMPs was discussed in RFC 1, the first of a series of standardization documents published by what later became the Internet Engineering Task Force (IETF).

History

The concept of an interface computer for computer networking was first proposed in 1966 by Donald Davies for the NPL network in England and implemented there in 1968–9. The same idea was independently developed in early 1967 at a meeting of principal investigators for the Department of Defense's Advanced Research Projects Agency (ARPA) to discuss interconnecting machines across the country. Larry Roberts, who led the ARPANET implementation, initially proposed a network of host computers. Wes Clark suggested inserting "a small computer between each host computer and the network of transmission lines", i.e. making the IMP a separate computer. The IMPs were built by the Massachusetts-based company Bolt Beranek and Newman (BBN) in 1969. BBN was contracted to build four IMPs, the first being due at UCLA by Labor Day; the remaining three were to be delivered in one-month intervals thereafter, completing the entire network in a total of twelve months. When Massachusetts Senator Edward Kennedy learned of BBN's accomplishment in signing this million-dollar agreement, he sent a telegram congratulating the company for being contracted to build the "Interfaith Message Processor". The team working on the IMP called themselves the "IMP Guys":

Team Leader: Frank Heart Software: Willy Crowther, David Walden, Bernie Cosell and Paul Wexelblat Hardware: Severo Ornstein, Ben Barker Theory and collaboration with the above on the overall system design: Bob Kahn Other: Hawley Rising Added to IMP team later: Marty Thrope (hardware), Jim Geisman, Truett Thach (installation), Bill Bertell (Honeywell) BBN began programming work in February 1969 on modified Honeywell DDP-516s. The completed code was six thousand words long, and was written in the Honeywell 516 assembly language. The IMP software was produced primarily on a PDP-1, where the IMP code was written and edited, then run on the Honeywell. There was considerable technical interchange with the British team building the NPL network and Paul Baran at RAND but the BBN team independently developed significant aspects of the network's internal operation, such as routing, flow control, software design, and network control. BBN designed the IMP simply as "a messenger" that would only "store-and-forward". BBN designed only the host-to-IMP specification, leaving host sites to build individual host-to-host interfaces. The IMP had an error-control mechanism that discarded packets with errors without acknowledging receipt; the source IMP, upon not receiving an acknowledging receipt, would subsequently re-send a duplicate packet. Based on the requirements of ARPA's request for proposal, the IMP used a 24-bit checksum for error correction. BBN chose to make the IMP hardware calculate the checksum, because it was a faster option than using a software calculation. The IMP was initially conceived as being connected to one host computer per site, but at the insistence of researchers and students from the host sites, each IMP was ultimately designed to connect to multiple host computers. The first IMP was delivered to Leonard Kleinrock's group at UCLA on August 30, 1969. It used an SDS Sigma 7 host computer. Douglas Engelbart's group at the Stanford Research Institute (SRI) received the second IMP on October 1, 1969. It was attached to an SDS 940 host. The third IMP was installed in University of California, Santa Barbara on November 1, 1969. The fourth IMP was installed in the University of Utah in December 1969. The first communication test between two systems (UCLA and SRI) took place on October 29, 1969, when a login to the SRI machine was attempted, but only the first two letters could be transmitted. The SRI machine crashed upon reception of the 'g' character. A few minutes later, the bug was fixed and the login attempt was successfully completed. BBN developed a program to test the performance of the communication circuits. According to a report filed by Heart, a preliminary test in late 1969 based on a 27-hour period of activity on the UCSB-SRI line found "approximately one packet per 20,000 in error;" subsequent tests "uncovered a 100% variation in this number - apparently due to many unusually long periods of time (on the order of hours) with no detected errors." A variant of the IMP existed, called the TIP (Terminal IMP), which connected terminals (i.e., teletypes) as well as computers to the network; it was based on the Honeywell 316, a later version of the 516. Later, some Honeywell-based IMPs were replaced with multiprocessing BBN Pluribus IMPs, but ultimately BBN developed a microprogrammed clone of the Honeywell machine. IMPs were at the heart of the ARPANET until DARPA decommissioned the ARPANET in 1989. Most IMPs were either taken apart, junked or transferred to MILNET. Some became artifacts in museums; Kleinrock placed IMP Number One on public view at UCLA. The last IMP on the ARPANET was the one at the University of Maryland.

… excerpt ends here. Continue reading the full article.

Illustrations

Interface Message Processor illustration
Interface Message Processor: IMP team (left to right): Truett Thatch, Bill Bartell (Honeywell), Dave Walden, Jim Geisman, Robert Kahn, Frank Heart, Ben Barker, Marty Thorpe, Will Crowther, and Severo Ornstein Not pictured: Bernie Cosell
IMP team (left to right): Truett Thatch, Bill Bartell (Honeywell), Dave Walden, Jim Geisman, Robert Kahn, Frank Heart, Ben Barker, Marty Thorpe, Will Crowther, and Severo Ornstein Not pictured: Bernie Cosell
Interface Message Processor: The front panel of the first IMP, taken at the opening of the Kleinrock Internet Heritage Site and Archive
The front panel of the first IMP, taken at the opening of the Kleinrock Internet Heritage Site and Archive

Worked examples

Example 1 — a first encounter with Interface Message Processor

Start with the simplest possible case. Write down what Interface Message Processor claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Interface Message Processor before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Interface Message Processor ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Interface Message Processor

In research
Interface Message Processor appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Interface Message Processor in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Interface Message Processor is common in secondary-school and first-year university syllabi. It links to neighbouring topics ARPANET, Computer-related introductions in 1969, History of the Internet, so understanding it makes those chapters shorter.
In everyday life
Look for Interface Message Processor outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Interface Message Processor in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Interface Message Processor means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Interface Message Processor out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Interface Message Processor in simple terms?

The Interface Message Processor (IMP) was the packet switching node used to interconnect participant networks to the ARPANET from the late 1960s to 1989. It was the first generation of gateways, which are known today as routers.

Why does Interface Message Processor matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Interface Message Processor?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Interface Message Processor.

Tags

  • ARPANET
  • Computer-related introductions in 1969
  • History of the Internet
  • Network protocols
  • Networking hardware

Keep exploring