Proceedings of the November 16-18, 1971, Fall Joint Computer Conference on - AFIPS '71 (Fall) 1971
DOI: 10.1145/1478873.1478906
|View full text |Cite
|
Sign up to set email alerts
|

The terminal IMP for the ARPA computer network

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
11
0

Year Published

1974
1974
2018
2018

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 44 publications
(11 citation statements)
references
References 7 publications
0
11
0
Order By: Relevance
“…Because these functions were felt to be generally useful , they were made accessible to all network users without requiring them to first log into one of the RSEXEC host systems. This has been particularly beneficial to the many users who access the ARPANET via TIPs [72], mini-h osts designed to provide terminal access to the network for users who are remote from the hosts they normally use . The TIP itself provides no computational or user services beyond the ability to "connec t" a terminal to a remote host.…”
Section: Nos Studymentioning
confidence: 99%
“…Because these functions were felt to be generally useful , they were made accessible to all network users without requiring them to first log into one of the RSEXEC host systems. This has been particularly beneficial to the many users who access the ARPANET via TIPs [72], mini-h osts designed to provide terminal access to the network for users who are remote from the hosts they normally use . The TIP itself provides no computational or user services beyond the ability to "connec t" a terminal to a remote host.…”
Section: Nos Studymentioning
confidence: 99%
“…Te TIP as d scribed by Ornstem et. al [44]. is characterized in Figure 7 e. The TIP uses 5% of its processing capacity to act as an IMP.…”
Section: Communication Facilitiesmentioning
confidence: 99%
“…The protocols and architectures used in mobile ad hoc networks (MANET) today [1]- [3] still reflect the severe memory and processing constraints imposed on computing equipment dedicated to communication tasks 40 years ago [4]- [6]. Because of such constraints, the protocols used in the ARPANET had to be organized into a stack in which most protocols were decoupled from the physical medium, each protocol layer operated independently of other, and processing and storage "inside" the network was kept to a minimum.…”
Section: Introductionmentioning
confidence: 99%
“…MANETs are very different than a wired network due to node mobility, the characteristics of radio channels, and the relative scarcity of bandwidth (compared to fiber). The in-network processing and storage power available even in small mobile nodes (e.g., PDAs, cellular phones) today are orders of magnitude larger than what was available inside a network more than 40 years ago [6]. Furthermore, while there were compeling cost reasons for a division of labor between hosts and routers (switches) 40 years ago, the wireless portions of the Internet need to be ubiquitous and invisible, each node of a MANET must act as a host and a router, and providing the user with the service or content she wants is far more important than trying to attain high link utilization.…”
Section: Introductionmentioning
confidence: 99%